| 2 | Approval of Agenda | |
|---|---|---|
| R1-2108690 | Draft Agenda of RAN1#106bis-e meeting | RAN1 Chair |
| R1-2108693 | RAN1#106bis-e Meeting Invitation, Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| R1-2108694 | Additional Guidelines for RAN1#106bis-e-Meeting Management | RAN1 Chair |
| R1-2109369 | Draft Agenda of RAN1#106bis-e meeting | RAN1 Chair |
| R1-2110520 | Draft Agenda of RAN1#106bis-e meeting | RAN1 Chair |
| R1-2110531 | RAN1#106bis-e Meeting Invitation, Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| 3 | Highlights from RAN plenary | |
| R1-2108691 | Highlights from RAN#93-e | RAN1 Chair |
| 4 | Approval of Minutes from previous meetings | |
| R1-2108692 | Report of RAN1#106-e meeting | ETSI MCC |
| R1-2110429 | Report of RAN1#106-e meeting | ETSI MCC |
| R1-2110434 | Report of RAN1#106-e meeting | ETSI MCC |
| 5 | Incoming Liaison Statements | |
| R1-2108696 | Reply LS on granularity of response time | RAN2, Huawei |
| R1-2108697 | Reply LS on Positioning Reference Units | RAN3, Ericsson |
| R1-2108698 | Reply LS on determination of location estimates in local co-ordinates | RAN3, Huawei |
| R1-2108699 | Reply LS on broadcast of NTN GW or gNB position | SA1, Huawei |
| R1-2108700 | LS on specification impact for methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | RAN4, Nokia |
| R1-2108701 | LS on scell dropping issue of CA | RAN4, Huawei |
| R1-2108702 | Reply LS on the maximum/minimum channel bandwidth and channelization for NR operation in 52.6 to 71 GHz | RAN4, Ericsson |
| R1-2108703 | Reply LS on PUCCH and PUSCH transmissions | RAN4, Qualcomm |
| R1-2108704 | LS on beam information of PUCCH Scell in PUCCH SCell activation procedure | RAN4, Huawei |
| R1-2108705 | Reply LS on NTN UL time and frequency synchronization requirements | RAN4, Xiaomi |
| R1-2108706 | Reply LS on PRS processing samples | RAN4, Ericsson |
| R1-2108707 | Reply LS on UE/TRP Tx/Rx timing error mitigation | RAN4, CATT |
| R1-2108708 | Reply LS on temporary RS for efficient SCell activation in NR CA | RAN4, Huawei |
| R1-2108709 | Reply LS to Half-duplex FDD switching for RedCap UE | RAN4, Ericsson |
| R1-2108710 | LS to RAN1 on RAN2 Agreements Related to Resource Selection | RAN2, InterDigital |
| R1-2108711 | Reply LS to RAN1 on on-demand DL PRS parameters | RAN2, Intel |
| R1-2108712 | LS on Msg3 repetition in coverage enhancement | RAN2, ZTE |
| R1-2108713 | LS to RAN1 on L2 buffer size reduction | RAN2, Intel, Spreadtrum |
| R1-2108714 | LS on capability related RAN2 agreements for RedCap | RAN2, Ericsson |
| R1-2108715 | LS on agreements related to SDT | RAN2, ZTE |
| R1-2108716 | LS on UE Power Saving | RAN2, MediaTek |
| R1-2108717 | LS on inter-cell beam management and multi-TRP in Rel-17 | RAN2, Nokia |
| R1-2108718 | Reply LS on determination of location estimates in local co-ordinates | RAN2, Ericsson |
| R1-2108719 | Reply LS on inter-donor migration | RAN2, Samsung |
| R1-2108775 | Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | Huawei, HiSilicon |
| R1-2108776 | Reply LS on Scell dropping issue of CA | Huawei, HiSilicon |
| R1-2108816 | Discussion on RAN4 LS on synchronous operation between Uu and SL | Nokia, Nokia Shanghai Bell |
| R1-2108817 | Discussion on RAN2 LS on RAN2 Agreements Related to Resource Selection | Nokia, Nokia Shanghai Bell |
| R1-2108838 | [DRAFT] Reply LS on Msg3 repetition in coverage enhancement | ZTE |
| R1-2108863 | [DRAFT] Reply LS on PUCCH and PUSCH transmissions | ZTE |
| R1-2108892 | About the LS on Status Update on XR Traffic Model | ZTE, Sanechips |
| R1-2108893 | Discussion on RAN2 LS on L2 buffer size reduction | Spreadtrum Communications |
| R1-2108942 | Discussion on RAN2 LS on Msg3 repetition in coverage enhancement | vivo |
| R1-2108943 | Discussion on RAN4 Reply LS on PUCCH and PUSCH transmissions | vivo |
| R1-2108944 | Draft Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | vivo |
| R1-2108945 | Draft reply LS on synchronous operation between Uu and SL in TDD band | vivo |
| R1-2108946 | Draft reply LS on RAN2 Agreements Related to Resource Selection | vivo |
| R1-2108947 | Draft reply LS on Scell dropping issue of CA | vivo |
| R1-2108948 | Discussion on RAN4 LS regarding methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | vivo |
| R1-2109027 | Discussion on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | ZTE |
| R1-2109028 | [DRAFT] Reply LS on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | ZTE |
| R1-2109048 | Discussion on "LS on scell dropping issue of CA" | OPPO |
| R1-2109049 | Discussion on LS on inter-cell beam management and multi-TRP in Rel-17 | OPPO |
| R1-2109058 | Discussion on LS to RAN1 on parameters for on-demand PRS | OPPO |
| R1-2109062 | Discussion on the relationship between SL DRX and resource selection | OPPO |
| R1-2109063 | Draft reply LS on LS about SL resource selection | OPPO |
| R1-2109064 | Discussion on synchronous operation between Uu and SL in TDD band | OPPO |
| R1-2109065 | Draft reply LS on synchronous operation between Uu and SL in TDD band | OPPO |
| R1-2109113 | Discussion of SA4 input on XR traffic | Ericsson |
| R1-2109114 | Draft reply LS on inter-cell beam management and multi-TRP in Rel-17 | vivo |
| R1-2109139 | [Draft] Reply LS on Scell dropping issue of CA | ZTE |
| R1-2109181 | Discussion on LS on RAN2 Agreements Related to Resource Selection | CATT, GOHIGH |
| R1-2109182 | Discussion on LS on synchronous operation between Uu and SL in TDD band | CATT, GOHIGH |
| R1-2109183 | Draft Reply LS on synchronous operation between Uu and SL in TDD band | CATT, GOHIGH |
| R1-2109257 | Draft reply LS on inter-cell beam management and multi-TRP in Rel-17 | ZTE |
| R1-2109331 | Discussion on RAN2 reply LS on UE capabilities for RedCap | ZTE, Sanechips |
| R1-2109370 | Reply LS to RAN2 on the capability of transparent TxD | RAN4, vivo |
| R1-2109371 | LS on R17 NR MG enhancements – Concurrent MG | RAN4, CATT, MediaTek |
| R1-2109372 | LS on criteria for RLM/BFD relaxation | RAN4, vivo, MediaTek |
| R1-2109373 | Reply LS on inter-donor migration | RAN4, ZTE Corporation |
| R1-2109374 | Reply LS on TCI state updates for L1/L2 centric inter-cell mobility | RAN4, Ericsson |
| R1-2109375 | LS on Rel-17 FeMIMO WI objective on link recovery procedure in FR2 serving cell | RAN4, vivo |
| R1-2109376 | Draft Reply LS to RAN2 LS on on inter-cell beam management and multi-TRP in Rel-17 | Xiaomi |
| R1-2109461 | Draft Reply LS on RAN2 Agreements Related to Resource Selection | Samsung |
| R1-2109462 | Draft Reply to RAN2 LS on UE Power Saving | Samsung |
| R1-2109463 | Draft Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | Samsung |
| R1-2109464 | Draft Reply LS on inter-cell beam management and multi-TRP in Rel-17 | Samsung |
| R1-2109550 | Draft reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | MediaTek Inc. |
| R1-2109566 | Discussion on RAN2 LS on broadcast session delivery about MCCH design | MediaTek Inc. |
| R1-2109580 | Discussion on RAN2 LS on UE Power Saving | MediaTek Inc. |
| R1-2109587 | [Draft] Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | ZTE |
| R1-2109588 | Discussion on RAN2 LS on Msg3 repetition in coverage enhancement | Intel Corporation |
| R1-2109589 | Response to RAN2 LS Related to Resource Selection | Intel Corporation |
| R1-2109735 | Discussion on RAN2 LS on resource selection within DRX | ZTE, Sanechips |
| R1-2109736 | Discussion on synchronous operation between Uu and SL in TDD band | ZTE, Sanechips |
| R1-2109859 | Discussion on LS to RAN1 on RAN2 Agreements Related to Resource Selection | LG Electronics |
| R1-2109869 | Draft reply LS to RAN 2 LS on inter-cell beam management and multi-TRP in Rel-17 | Nokia, Nokia Shanghai Bell |
| R1-2109882 | Discussion on RAN2 LS on RA for transmission to Rx UEs in DRX | InterDigital, Inc. |
| R1-2109900 | [DRAFT] Reply LS on inter-cell beam management and multi-TRP in Rel-17 | Lenovo, Motorola Mobility |
| R1-2109947 | Discussion on LS reply on inter-cell beam management and multi-TRP in Rel-17 | Intel Corporation |
| R1-2110008 | Draft Reply LS on Inter-cell Beam Management and Multi-TRP | Apple |
| R1-2110009 | Discussion on RAN4 LS R1-2108704 on beam information of PUCCH Scell in PUCCH SCell activation procedure | Apple |
| R1-2110010 | Discussion on RAN4 LS on irregular channel bandwidths | Apple |
| R1-2110011 | Draft Reply to RAN4 LS on irregular channel bandwidths | Apple |
| R1-2110076 | Draft reply LS to RAN2 on inter-cell beam management and multi-TRP in Rel-17 | LG Electronics |
| R1-2110094 | Draft Reply LS on PUCCH and PUSCH repetitions | LG Electronics |
| R1-2110095 | Draft Reply LS on Msg3 repetition in coverage enhancement | LG Electronics |
| R1-2110135 | Draft Reply to RAN4 LS on SCell dropping issue of CA | Ericsson |
| R1-2110156 | Draft reply to RAN2 LS to RAN1 on RAN2 Agreements Related to Resource Selection | Qualcomm Incorporated |
| R1-2110157 | Draft Reply to RAN4 LS on synchronous operation between Uu and SL in TDD band | Qualcomm Incorporated |
| R1-2110158 | Discussion on LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | Qualcomm Incorporated |
| R1-2110159 | Draft reply LS on inter-cell beam management and multi-TRP in Rel-17 | Qualcomm Incorporated |
| R1-2110160 | Draft reply LS on Msg3 repetition in coverage enhancement | Qualcomm Incorporated |
| R1-2110161 | Discussion on UL MIMO Coherence capability | Qualcomm Incorporated |
| R1-2110162 | Discussion on LS on SCell dropping issue of CA | Qualcomm Incorporated |
| R1-2110296 | DRAFT LS on specification impact for methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | Nokia, Nokia Shanghai Bell |
| R1-2110304 | On efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | Ericsson |
| R1-2110335 | [Draft] Reply LS on RAN2 Agreements Related to Resource Selection | Ericsson |
| R1-2110336 | [Draft] Reply LS on synchronous operation between Uu and SL in TDD band | Ericsson |
| R1-2110337 | Discussion on RAN4 LS on synchronous operation between Uu and SL in TDD band | Ericsson |
| R1-2110338 | DRX impacts on resource selection procedures | Ericsson |
| R1-2110346 | Discussion of RAN2 LS on inter-cell BM and mTRP | Ericsson |
| R1-2110359 | Discussion Reply on PUCCH and PUSCH Transmissions | Ericsson |
| R1-2110360 | Draft Reply on Msg3 Repetition in Coverage Enhancement | Ericsson |
| R1-2110361 | Discussion on LS on Status Update on XR Traffic | Huawei, HiSilicon |
| R1-2110362 | Discussion on LS on Msg3 PUSH repetition | Huawei, HiSilicon |
| R1-2110363 | Views on RAN2 LS for inter-cell BM in R17 | Huawei, HiSilicon |
| R1-2110364 | Discussion on RAN4 LS on synchronous operation between Uu and SL in TDD band | Huawei, HiSilicon |
| R1-2110365 | Discussion on RAN2 LS on resource selection with DRX | Huawei, HiSilicon |
| R1-2110366 | Discussion on RAN4 LS on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | Huawei, HiSilicon |
| R1-2110367 | Discussion on RAN2 LS on UE Power Saving | Huawei, HiSilicon |
| R1-2110368 | Discussion on RAN4 reply LS on PRS processing samples | Huawei, HiSilicon |
| R1-2110369 | Discussion on RAN4 reply LS on UE/TRP Rx/Tx timing error mitigation | Huawei, HiSilicon |
| R1-2110370 | Discussion on RAN4 LS on PUCCH and PUSCH repetition | Huawei, HiSilicon |
| R1-2110498 | Incoming LS handling for RAN1#106bis-e | RAN1 Chair |
| R1-2110564 | [106bis-e-AI5-LSs-01] Moderator summary | Moderator (Nokia) |
| R1-2110565 | [DRAFT] Reply LS on specification impact for methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | Nokia |
| R1-2110584 | Reply LS on specification impact for methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths | RAN1, Nokia |
| R1-2110655 | Summary of email discussion [106bis-e-AI5-LSs-02] on reply LS to R1-2108704 | Moderator (Huawei) |
| 5.1 | RAN1 Aspects for RF requirements for NR frequency range 1 (FR1) | |
| R1-2108743 | Discussions on enhancements for UL Tx switching | Huawei, HiSilicon |
| R1-2108839 | Remaining issues for Rel-17 UL Tx switching | ZTE |
| R1-2108949 | Remaining issues on Rel-17 Tx switching | vivo |
| R1-2109050 | Discussion on Rel-17 Tx switching enhancement | OPPO |
| R1-2109246 | Remaining issues on Rel-17 uplink Tx switching | China Telecom |
| R1-2109269 | Discussion on Rel-17 UL Tx Switching | CMCC |
| R1-2110163 | Discussion on R17 UL Tx switching | Qualcomm Incorporated |
| R1-2110566 | [106bis-e-NR-R17-TxSwitching-01] Summary of email discussion on Rel-17 uplink Tx switching | Moderator (China Telecom) |
| R1-2110656 | Draft reply LS on Scell dropping issue of CA | Moderator (Huawei) |
| R1-2110660 | Reply LS on SCell dropping issue of CA | RAN1, Huawei |
| R1-2110668 | Summary of email discussion [106bis-e-NR-SCell-Dropping] on reply LS to R1-2108701 | Moderator (Huawei) |
| R1-2110687 | RAN1 agreements for Rel-17 Tx switching | WI rapporteur (China Telecom) |
| R1-2110698 | Reply LS on SCell dropping issue of CA | RAN1, Huawei |
| 5.2 | RAN1 Aspects for NR small data transmissions in INACTIVE state | |
| R1-2108752 | Physical layer aspects of CG-SDT | Huawei, HiSilicon |
| R1-2108894 | Discussion on physical layer aspects of small data transmission | Spreadtrum Communications |
| R1-2108950 | Discussion on RAN1 impacts for small data transmission | vivo |
| R1-2109026 | Discussion on remaining physical layer issues of small data transmission | ZTE, Sanechips |
| R1-2109377 | Physical layer aspects for NR small data transmissions in INACTIVE state | Xiaomi |
| R1-2109465 | Discussion on physical layer aspects for NR small data transmissions in INACTIVE state | Samsung |
| R1-2109590 | Discussion on physical layer aspects of small data transmission | Intel Corporation |
| R1-2109727 | Discussion on L1 feedback for CG-SDT | Sierra Wireless. S.A. |
| R1-2109762 | Physical layer aspects for NR small data transmissions in INACTIVE state | L.M. Ericsson Limited |
| R1-2109771 | Remaining issues of physical layer aspects for SDT | Sony |
| R1-2109911 | Physical layer aspects of small data transmission | InterDigital, Inc. |
| R1-2109960 | Discussion on physical layer aspects of small data transmission | LG Electronics |
| R1-2110012 | Discussion on physical layer aspects of small data transmission | Apple |
| R1-2110164 | Discussion on PHY Impacts of SDT | Qualcomm Incorporated |
| R1-2110297 | On physical layer aspects of small data transmission | Nokia, Nokia Shanghai Bell |
| R1-2110495 | Summary on the physical layer aspects of small data transmission | Moderator (ZTE) |
| R1-2110556 | [Draft] Reply LS on the physical layer aspects of small data transmission | ZTE |
| R1-2110661 | Reply LS on the physical layer aspects of small data transmission | RAN1, ZTE |
| R1-2110693 | RAN1 agreements for Rel-17 WI on SDT | Moderator(ZTE) |
| 8 | Release 17 | |
| R1-2110415 | Recommendations for RAN1 RRC Parameter Preparation | Moderator (Ericsson) |
| R1-2110571 | DRAFT LS on Re-17 LTE and NR higher-layers parameter list | Moderator (Ericsson) |
| R1-2110572 | Consolidated higher layers parameter list for Rel-17 LTE | Moderator (Ericsson) |
| R1-2110573 | Consolidated higher layers parameter list for Rel-17 NR | Moderator (Ericsson) |
| R1-2110575 | LS on Re-17 LTE and NR higher-layers parameters list | RAN1, Ericsson |
| R1-2110654 | Summary of Email discussion on Rel-17 RRC parameters for LS to RAN2 | Moderator (Ericsson) |
| R1-2110680 | Collection of higher layers parameter list for Rel-17 LTE and NR | Moderator (Ericsson) |
| 8.1 | Further enhancements on MIMO for NR | |
| R1-2110635 | Moderator summary for Rel-17 NR_FeMIMO RRC parameters | Moderator (Samsung) |
| 8.1.1 | Enhancements on Multi-beam Operation | |
| R1-2108756 | Enhancements on multi-beam operation in Rel-17 | Huawei, HiSilicon |
| R1-2108796 | Enhancement on multi-beam operation | FUTUREWEI |
| R1-2108808 | Further Discussion on Enhancements for Multi-beam Operation | InterDigital, Inc. |
| R1-2108870 | Enhancements on Multi-beam Operation | ZTE |
| R1-2108895 | Enhancements on Multi-beam Operation | Spreadtrum Communications |
| R1-2108951 | Further discussion on multi beam enhancement | vivo |
| R1-2109029 | Enhancements on Multi-beam Operation | Fujitsu |
| R1-2109038 | Enhancements on Multi-beam Operation | OPPO |
| R1-2109103 | Enhancements on Multi-beam Operation | Lenovo, Motorola Mobility |
| R1-2109110 | Remaining issues on multi-beam enhancements | Ericsson |
| R1-2109122 | Discussion on multi-beam operation | NEC |
| R1-2109180 | Enhancements on multi-beam operation | TCL Communication Ltd. |
| R1-2109184 | Futher discussion on Rel-17 multi-beam operation | CATT |
| R1-2109270 | Enhancements on multi-beam operation | CMCC |
| R1-2109350 | Enhancements on multi-beam operation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2109378 | Enhancements on multi-beam operation | Xiaomi |
| R1-2109466 | Moderator summary for multi-beam enhancement | Moderator (Samsung) |
| R1-2109467 | Summary of offline discussion on unified TCI and inter-cell beam management | Moderator (Samsung) |
| R1-2109468 | Multi-Beam Enhancements | Samsung |
| R1-2109543 | Enhancement on multi-beam operation | MediaTek Inc. |
| R1-2109591 | Enhancements to Multi-Beam Operations | Intel Corporation |
| R1-2109658 | Discussion on multi-beam operation | NTT DOCOMO, INC. |
| R1-2109772 | Further enhancement on multi-beam operation | Sony |
| R1-2109832 | Discussion of enhancements on multi-beam operation | FGI, Asia Pacific Telecom |
| R1-2109870 | Enhancements on Multi-beam Operation | Nokia, Nokia Shanghai Bell |
| R1-2109923 | Enhancements on Multi-Beam Operations | AT&T |
| R1-2110013 | Views on Rel-17 Beam Management enhancement | Apple |
| R1-2110077 | Enhancements on Multi-beam Operation | LG Electronics |
| R1-2110103 | Enhancements on Multi-beam Operation | Convida Wireless |
| R1-2110165 | Enhancements on Multi-beam Operation | Qualcomm Incorporated |
| R1-2110492 | Moderator summary#2 for multi-beam enhancement: ROUND 1 | Moderator (Samsung) |
| R1-2110514 | Moderator summary#3 for multi-beam enhancement: ROUND 2 | Moderator (Samsung) |
| R1-2110549 | Moderator summary#4 for multi-beam enhancement: ROUND 3 | Moderator (Samsung) |
| R1-2110630 | Moderator summary for LS reply to RAN2 on inter-cell beam management and multi-TRP in Rel-17 | Moderator (Nokia) |
| R1-2110631 | LS Reply on inter-cell beam management and multi-TRP in Rel-17 | RAN1, Nokia |
| 8.1.2.1 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | |
| R1-2108757 | Enhancements on multi-TRP for reliability and robustness in Rel-17 | Huawei, HiSilicon |
| R1-2108790 | Multi-TRP/panel for non-PDSCH | FUTUREWEI |
| R1-2108809 | Remaining Details on Enhancements for PDCCH, PUCCH, and PUSCH | InterDigital, Inc. |
| R1-2108871 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | ZTE |
| R1-2108896 | Discussion on enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Spreadtrum Communications |
| R1-2108952 | Further discussion on Multi-TRP for PDCCH, PUCCH and PUSCH enhancements | vivo |
| R1-2109030 | Enhancements on Multi-TRP for PDCCH PUCCH and PUSCH | Fujitsu |
| R1-2109039 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | OPPO |
| R1-2109104 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Lenovo, Motorola Mobility |
| R1-2109109 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | TCL Communication Ltd. |
| R1-2109123 | Discussion on multi-TRP for PDCCH, PUCCH and PUSCH | NEC |
| R1-2109185 | On multi-TRP/panel PDCCH, PUCCH and PUSCH transmission | CATT |
| R1-2109271 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | CMCC |
| R1-2109351 | On multi-TRP enhancements for PDCCH | Fraunhofer IIS, Fraunhofer HHI |
| R1-2109379 | Enhancements on Multi-TRP for PDCCH, PUSCH and PUCCH | Xiaomi |
| R1-2109469 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Samsung |
| R1-2109544 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | MediaTek Inc. |
| R1-2109592 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | Intel Corporation |
| R1-2109659 | Discussion on MTRP for reliability | NTT DOCOMO, INC. |
| R1-2109773 | Considerations on Multi-TRP for PDCCH, PUCCH, PUSCH | Sony |
| R1-2109824 | Discussion on enhancements on multi-TRP for uplink channels | FGI, Asia Pacific Telecom |
| R1-2109871 | Enhancements for Multi-TRP URLLC schemes | Nokia, Nokia Shanghai Bell |
| R1-2110014 | Views on Rel-17 multi-TRP reliability enhancement | Apple |
| R1-2110078 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | LG Electronics |
| R1-2110104 | Multi-TRP Enhancements for PDCCH | Convida Wireless |
| R1-2110166 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Qualcomm Incorporated |
| R1-2110286 | Discussion on mTRP PXXCH | ASUSTeK |
| R1-2110289 | Remaining issues on PDCCH, PUSCH and PUCCH enhancements for multi-TRP | Ericsson |
| R1-2110438 | Summary #1 of [106bis-e-NR-feMIMO-02] Email discussion on multi-TRP for PDCCH | Moderator (Qualcomm) |
| R1-2110439 | Summary #2 of [106bis-e-NR-feMIMO-02] Email discussion on multi-TRP for PDCCH | Moderator (Qualcomm) |
| R1-2110440 | Summary #3 of [106bis-e-NR-feMIMO-02] Email discussion on multi-TRP for PDCCH | Moderator (Qualcomm) |
| R1-2110468 | Summary #1 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| R1-2110469 | Summary #2 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| R1-2110470 | Summary #3 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| 8.1.2.2 | Enhancements on Multi-TRP inter-cell operation | |
| R1-2108758 | Enhancements on inter-cell multi-TRP operation in Rel-17 | Huawei, HiSilicon |
| R1-2108791 | Inter-cell multi-TRP operation | FUTUREWEI |
| R1-2108810 | Further Details on M-TRP Inter-cell Operation | InterDigital, Inc. |
| R1-2108872 | Discussion on Multi-TRP inter-cell operation | ZTE |
| R1-2108897 | Discussion on enhancements on multi-TRP inter-cell operation | Spreadtrum Communications |
| R1-2108953 | Further discussion on inter-cell MTRP operation | vivo |
| R1-2109040 | Enhancement on inter-cell multi-TRP operation | OPPO |
| R1-2109105 | Enhancements on Multi-TRP inter-cell operation | Lenovo, Motorola Mobility |
| R1-2109124 | Discussion on multi-TRP inter-cell operation | NEC |
| R1-2109186 | Discussion on inter-cell operation for multi-TRP/panel | CATT |
| R1-2109272 | Enhancements on Multi-TRP inter-cell operation | CMCC |
| R1-2109380 | Disscussion on Multi-TRP Inter-cell operation | Xiaomi |
| R1-2109470 | Enhancements on Multi-TRP inter-cell operation | Samsung |
| R1-2109593 | Multi-TRP enhancements for inter-cell operation | Intel Corporation |
| R1-2109660 | Discussion on inter-cell multi-TRP operation | NTT DOCOMO, INC. |
| R1-2109834 | Finalizing inter-cell multi-TRP operation | Ericsson |
| R1-2109872 | Enhancements to enable inter-cell multi-TRP operations | Nokia, Nokia Shanghai Bell |
| R1-2110015 | Views on Rel-17 Inter-cell multi-TRP operation | Apple |
| R1-2110079 | Enhancements on Multi-TRP inter-cell operation | LG Electronics |
| R1-2110111 | Discussion on Multi-TRP inter-cell operation | ASUSTEK |
| R1-2110167 | Enhancements on Multi-TRP inter-cell operation | Qualcomm Incorporated |
| R1-2110482 | Feature lead summary#1 on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| 8.1.2.3 | Enhancements on beam management for multi-TRP | |
| R1-2108759 | Enhancements on beam management for multi-TRP in Rel-17 | Huawei, HiSilicon |
| R1-2108792 | Beam management for simultaneous multi-TRP transmission with multi-panel reception | FUTUREWEI |
| R1-2108811 | On Beam Management Enhancements for Multi-TRP | InterDigital, Inc. |
| R1-2108873 | Enhancements on beam management for Multi-TRP | ZTE |
| R1-2108898 | Discussion on enhancements on beam management for multi-TRP | Spreadtrum Communications |
| R1-2108954 | Further discussion on MTRP multibeam enhancement | vivo |
| R1-2109031 | Enhancements on beam management for multi-TRP | Fujitsu |
| R1-2109041 | Enhancements on beam management for multi-TRP | OPPO |
| R1-2109106 | Enhancements on beam management for multi-TRP | Lenovo, Motorola Mobility |
| R1-2109108 | Enhancements on beam management for multi-TRP | TCL Communication Ltd. |
| R1-2109125 | Discussion on beam management for multi-TRP | NEC |
| R1-2109187 | Beam reporting and beam failure recovery for multi-TRP | CATT |
| R1-2109273 | Enhancements on beam management for multi-TRP | CMCC |
| R1-2109381 | Enhancement on beam management for Multi-TRP | Xiaomi |
| R1-2109471 | Enhancements on beam management for multi-TRP | Samsung |
| R1-2109545 | Enhancement on beam management for multi-TRP | MediaTek Inc. |
| R1-2109594 | Multi-TRP enhancements for beam management | Intel Corporation |
| R1-2109661 | Discussion on beam management for MTRP | NTT DOCOMO, INC. |
| R1-2109774 | Enhancements on beam management for multi-TRP | Sony |
| R1-2109807 | Enhancements on beam management for multi-TRP | ETRI |
| R1-2109833 | Discussion of enhancements on beam management for multi-TRP | FGI, Asia Pacific Telecom |
| R1-2109873 | Enhancements on Beam Management for Multi-TRP/Panel Transmission | Nokia, Nokia Shanghai Bell |
| R1-2110016 | Views on Rel-17 multi-TRP BM enhancement | Apple |
| R1-2110080 | Enhancements on beam management for multi-TRP | LG Electronics |
| R1-2110106 | On Multi-TRP BFR | Convida Wireless |
| R1-2110114 | Discussion on beam management for multi-TRP | ASUSTEK |
| R1-2110168 | Enhancements on beam management for multi-TRP | Qualcomm Incorporated |
| R1-2110241 | Discussion on beam management for multi-TRP | ITRI |
| R1-2110288 | Remaining issues on beam management for multi-TRP | Ericsson |
| R1-2110494 | Summary of enhancements on beam management for multi-TRP (Round 1) | Moderator (CATT) |
| R1-2110576 | Summary of enhancements on beam management for multi-TRP (Round 3) | Moderator (CATT) |
| 8.1.2.4 | Enhancements on HST-SFN deployment | |
| R1-2108760 | Enhancements on HST multi-TRP deployment in Rel-17 | Huawei, HiSilicon |
| R1-2108793 | Enhancement to support HST-SFN deployment scenario | FUTUREWEI |
| R1-2108812 | Remaining Issues M-TRP Operation for HST-SFN Deployment | InterDigital, Inc. |
| R1-2108874 | Discussion on Multi-TRP HST enhancements | ZTE |
| R1-2108899 | Discussion on enhancements on HST-SFN deployment | Spreadtrum Communications |
| R1-2108955 | Further discussion on HST-SFN schemes | vivo |
| R1-2109042 | Enhancements on HST-SFN deployment | OPPO |
| R1-2109126 | Discussion on HST-SFN deployment | NEC |
| R1-2109188 | Further discussion on HST-SFN deployment | CATT |
| R1-2109274 | Enhancements on HST-SFN deployment | CMCC |
| R1-2109382 | Enhancements on HST-SFN operation for multi-TRP PDCCH transmission | Xiaomi |
| R1-2109472 | Enhancements on HST-SFN | Samsung |
| R1-2109546 | Enhancements on HST-SFN deployment | MediaTek Inc. |
| R1-2109595 | Enhancements to HST-SFN deployments | Intel Corporation |
| R1-2109662 | Discussion on HST-SFN deployment | NTT DOCOMO, INC. |
| R1-2109775 | Enhancements on HST-SFN deployment | Sony |
| R1-2109806 | Remaining issues on HST-SFN enhancements | Ericsson |
| R1-2109874 | Enhancements for HST-SFN deployment | Nokia, Nokia Shanghai Bell |
| R1-2109934 | Enhancements for HST-SFN deployment | Lenovo, Motorola Mobility |
| R1-2110017 | Views on Rel-17 HST enhancement | Apple |
| R1-2110081 | Enhancements on HST-SFN deployment | LG Electronics |
| R1-2110107 | On Enhancements for HST-SFN deployment | Convida Wireless |
| R1-2110169 | Enhancements on HST-SFN deployment | Qualcomm Incorporated |
| R1-2110430 | Summary#1 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2110496 | Summary#2 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2110548 | Summary#3 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| 8.1.3 | Enhancements on SRS flexibility, coverage and capacity | |
| R1-2108761 | Enhancements on SRS in Rel-17 | Huawei, HiSilicon |
| R1-2108794 | Enhancements on SRS flexibility, coverage and capacity | FUTUREWEI |
| R1-2108813 | Further Details on SRS Enhancements | InterDigital, Inc. |
| R1-2108875 | Enhancements on SRS flexibility, coverage and capacity | ZTE |
| R1-2108900 | Considerations on SRS enhancements | Spreadtrum Communications |
| R1-2108956 | Further discussion on SRS enhancement | vivo |
| R1-2109043 | Enhancements on SRS flexibility, coverage and capacity | OPPO |
| R1-2109107 | Enhancements on SRS | Lenovo, Motorola Mobility |
| R1-2109127 | Discussion on SRS enhancement | NEC |
| R1-2109189 | Further details on SRS enhancement for Rel-17 | CATT |
| R1-2109258 | FL summary #1 on SRS enhancements | Moderator (ZTE) |
| R1-2109275 | Enhancements on SRS flexibility, coverage and capacity | CMCC |
| R1-2109353 | Enhancements on SRS for coverage and capacity | Fraunhofer IIS, Fraunhofer HHI |
| R1-2109383 | Discussion on SRS enhancements | Xiaomi |
| R1-2109473 | Enhancements on SRS | Samsung |
| R1-2109547 | Enhancements on SRS flexibility, coverage and capacity | MediaTek Inc. |
| R1-2109596 | Discussion on SRS enhancements | Intel Corporation |
| R1-2109663 | Discussion on SRS enhancement | NTT DOCOMO, INC. |
| R1-2109875 | Enhancements on SRS flexibility, coverage and capacity | Nokia, Nokia Shanghai Bell |
| R1-2110018 | Views on Rel-17 SRS enhancement | Apple |
| R1-2110082 | Enhancements on SRS flexibility, coverage and capacity | LG Electronics |
| R1-2110121 | Remaining Issues for SRS | Ericsson |
| R1-2110170 | Enhancements on SRS flexibility, coverage and capacity | Qualcomm Incorporated |
| R1-2110475 | FL summary #2 on SRS enhancements | Moderator (ZTE) |
| R1-2110522 | FL summary #3 on SRS enhancements | Moderator (ZTE) |
| 8.1.4 | CSI enhancements: MTRP and FR1 FDD reciprocity | |
| R1-2108762 | CSI enhancements on MTRP and FDD in Rel-17 | Huawei, HiSilicon |
| R1-2108795 | CSI enhancement for multi-TRP and FDD | FUTUREWEI |
| R1-2108814 | On CSI Enhancements for NCJT MTRP | InterDigital, Inc. |
| R1-2108876 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | ZTE |
| R1-2108901 | Discussion on CSI enhancements for M-TRP and FR1 FDD reciprocity | Spreadtrum Communications |
| R1-2108957 | Further discussion on MTRP CSI and Partial reciprocity | vivo |
| R1-2109044 | CSI enhancement for M-TRP and FDD reciprocity | OPPO |
| R1-2109128 | Discussion on CSI enhancement for multi-TRP | NEC |
| R1-2109190 | Further details on CSI enhancement for Rel-17 | CATT |
| R1-2109276 | Enhancements on CSI reporting for Multi-TRP | CMCC |
| R1-2109352 | CSI enhancements on Type II PS codebook and multi-TRP | Fraunhofer IIS, Fraunhofer HHI |
| R1-2109474 | Views on Rel. 17 CSI enhancements | Samsung |
| R1-2109548 | CSI Enhancement for NCJT and FR1 FDD reciprocity | MediaTek Inc. |
| R1-2109597 | On CSI enhancements for MTRP and FDD | Intel Corporation |
| R1-2109664 | Discussion on CSI enhancements | NTT DOCOMO, INC. |
| R1-2109776 | Additional considerations on CSI enhancements | Sony |
| R1-2109876 | Enhancement on CSI measurement and reporting | Nokia, Nokia Shanghai Bell |
| R1-2109935 | CSI enhancements for multi-TRP and FDD reciprocity | Lenovo, Motorola Mobility |
| R1-2110019 | Views on Rel-17 CSI enhancement | Apple |
| R1-2110083 | CSI enhancements for Rel-17 | LG Electronics |
| R1-2110171 | CSI enhancements: MTRP and FR1 FDD reciprocity | Qualcomm Incorporated |
| R1-2110291 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | Ericsson |
| R1-2110420 | Summary of CSI enhancements for MTRP and FDD (Round 0) | Moderator (Huawei, HiSilicon) |
| R1-2110421 | Summary of CSI enhancements for MTRP and FDD (Round 1) | Moderator (Huawei, HiSilicon) |
| R1-2110422 | Summary of CSI enhancements for MTRP and FDD (Round 2) | Moderator (Huawei, HiSilicon) |
| R1-2110506 | Summary of CSI enhancements for MTRP and FDD (Round 3) | Moderator (Huawei, HiSilicon) |
| 8.1.5 | Other | |
| R1-2108815 | Results on Multi-Panel Multi-TRP MIMO | InterDigital, Inc. |
| R1-2108877 | Further details on Multi-beam and Multi-TRP operation | ZTE |
| R1-2108958 | Discussion on impact of cross-talk on UL performance | vivo |
| R1-2109045 | Discussion on further enhancements for multi-beam operation | OPPO |
| R1-2109475 | Additional enhancements for multi-beam | Samsung |
| R1-2109753 | Further considerations and simulations of CSI enhancement for Rel-17 | Huawei, HiSilicon |
| R1-2109836 | Our views on Rel.18 MIMO WI content | Ericsson |
| R1-2110020 | On Further MIMO Enhancement | Apple |
| 8.2 | Supporting NR from 52.6GHz to 71 GHz | |
| R1-2110612 | Session notes for 8.2 (Extending current NR operation to 71GHz) | Ad-Hoc Chair (Ericsson) |
| R1-2110681 | Comments collection for RRC parameters for extending NR to 52.6-71GHz | WI rapporteur (Qualcomm incorporated) |
| 8.2.1 | Initial access aspects | |
| R1-2108767 | Initial access signals and channels for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2108782 | Initial access for Beyond 52.6GHz | FUTUREWEI |
| R1-2108902 | Discussion on initial access aspects for NR for 60GHz | Spreadtrum Communications |
| R1-2108934 | Discussion on the initial access aspects for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2108959 | Discussions on initial access aspects for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2109032 | Considerations on initial access for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2109070 | Discussion on initial access aspects | OPPO |
| R1-2109120 | Discussion on initial access aspects supporting NR from 52.6 to 71 GHz | NEC |
| R1-2109208 | Initial access aspects for up to 71GHz operation | CATT |
| R1-2109401 | On initial access aspects for NR from 52.6-71 GHz | Xiaomi |
| R1-2109433 | Initial Access Aspects | Ericsson |
| R1-2109442 | Initial access aspects | Nokia, Nokia Shanghai Bell |
| R1-2109476 | Initial access aspects for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2109557 | Remaining issues on initial access of 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2109598 | Discussion on initial access aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2109665 | Initial access aspects for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2109741 | Initial access aspects for NR from 52.6 GHz to 71 GHz | Panasonic Corporation |
| R1-2109777 | Considerations on initial access aspects for NR from 52.6 GHz to 71 GHz | Sony |
| R1-2109808 | Discussion on initial access aspects for NR from 52.6 to 71GHz | ETRI |
| R1-2109897 | Initial access aspects for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2109903 | Discussion on initial access channels and signals for operation in 52.6-71GHz | InterDigital, Inc. |
| R1-2109961 | Initial access aspects to support NR above 52.6 GHz | LG Electronics |
| R1-2109992 | Initial access aspects | Sharp |
| R1-2110021 | Initial access signals and channels | Apple |
| R1-2110109 | NR SSB design consideration for 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2110172 | Initial access aspects for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2110320 | Discussion on initial access aspects for NR beyond 52.6GHz | WILUS Inc. |
| R1-2110404 | Issue Summary for initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2110405 | Summary #1 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2110516 | Summary #2 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2110537 | Summary #3 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2110538 | Summary #4 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2110634 | Summary #5 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| 8.2.2 | PDCCH monitoring enhancements | |
| R1-2108768 | Enhancement on PDCCH monitoring | Huawei, HiSilicon |
| R1-2108783 | PDCCH monitoring enhancements | FUTUREWEI |
| R1-2108887 | Discussion on PDCCH monitoring enhancements for above 52.6GHz | Transsion Holdings |
| R1-2108935 | Discussion on the PDCCH monitoring enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2108960 | Discussions on PDCCH monitoring enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2109071 | Discussion on PDCCH monitoring enhancement | OPPO |
| R1-2109117 | Discussion on PDCCH monitoring enhancements supporting NR from 52.6GHz to 71 GHz | NEC |
| R1-2109209 | PDCCH monitoring enhancements for up to 71GHz operation | CATT |
| R1-2109402 | PDCCH monitoring enhancement for NR 52.6-71GHz | Xiaomi |
| R1-2109434 | PDCCH Monitoring Enhancements | Ericsson |
| R1-2109443 | PDCCH monitoring enhancements | Nokia, Nokia Shanghai Bell |
| R1-2109477 | PDCCH monitoring enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2109560 | PDCCH monitoring enhancement for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2109599 | Discussion on PDCCH monitoring enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2109666 | PDCCH monitoring enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2109778 | PDCCH enhancement for NR from 52.6GHz to 71GHz | Sony |
| R1-2109898 | PDCCH monitoring enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2109904 | Discussions on PDCCH monitoring enhancements | InterDigital, Inc. |
| R1-2109962 | PDCCH monitoring enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2109993 | PDCCH monitoring enhancements | Sharp |
| R1-2110022 | PDCCH Enhancements for above 52.6 GHz | Apple |
| R1-2110110 | PDCCH Monitoring for NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2110173 | PDCCH monitoring enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2110248 | PDCCH monitoring enhancements | Charter Communications |
| R1-2110252 | PDCCH monitoring for NR operation from 52.6 to 71 GHz | Panasonic |
| R1-2110373 | Feature lead summary #1 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2110521 | Feature lead summary #2 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2110560 | Feature lead summary #3 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2110582 | Feature lead summary #4 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| 8.2.3 | Enhancements for PUCCH formats 0/1/4 | |
| R1-2108769 | Enhancement on PUCCH formats | Huawei, HiSilicon |
| R1-2108784 | On Enhancement of PUCCH Resource Set for 52.6GHz to 71GHz | FUTUREWEI |
| R1-2108936 | Discussion on the PUCCH enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2108961 | Discussions on PUCCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2109072 | Discussion on enhancements for PUCCH format 0/1/4 | OPPO |
| R1-2109210 | Enhancements for PUCCH formats for up to 71GHz operation | CATT |
| R1-2109435 | PUCCH enhancements | Ericsson |
| R1-2109436 | FL Summary for Enhancements for PUCCH formats 0/1/4 | Ericsson |
| R1-2109444 | Remaining items for enhanced PUCCH formats 0/1/4 | Nokia, Nokia Shanghai Bell |
| R1-2109478 | Enhancements for PUCCH format 0/1/4 for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2109600 | Discussion on PUCCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2109667 | PUCCH format 0/1/4 enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2109779 | Additional considerations on enhancements for PUCCH formats 0/1/4 | Sony |
| R1-2109905 | Discussions on enhancements for PUCCH formats 0/1/4 | InterDigital, Inc. |
| R1-2109963 | Enhancements for PUCCH formats 0/1/4 to support NR above 52.6 GHz | LG Electronics |
| R1-2110023 | Discussion on Enhancements for PUCCH formats 0/1/4 | Apple |
| R1-2110174 | Enhancements for PUCCH for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2110499 | FL Summary #2 for [106bis-e-NR-52-71GHz-03] Email discussion/approval on enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| 8.2.4 | Beam management for new SCSs | |
| R1-2108770 | Discussion on the beam management procedures for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2108785 | Views on Beam management for Beyond 52.6 GHz | FUTUREWEI |
| R1-2108903 | Discussion on beam management for above 52.6GHz | Spreadtrum Communications |
| R1-2108937 | Discussion on the beam management for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2108962 | Discussions on beam management for new SCSs for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2109073 | Discussion on beam management for new SCSs | OPPO |
| R1-2109119 | Beam management enhancement for NR from 52.6GHz to 71GHz | NEC |
| R1-2109211 | Beam management for new SCSs for up to 71GHz operation | CATT |
| R1-2109403 | Discussion on beam management for new SCSs | xiaomi |
| R1-2109437 | Beam Management for New SCSs | Ericsson |
| R1-2109445 | Beam Management Aspects | Nokia, Nokia Shanghai Bell |
| R1-2109479 | Beam management for new SCSs for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2109561 | Beam management discussion for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2109601 | Discussion on Beam management aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2109668 | Beam based operation for new SCSs for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2109780 | Beam management enhancement for NR from 52.6GHz to 71GHz | Sony |
| R1-2109899 | Beam-management enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2109906 | Discussions on beam management for new SCSs | InterDigital, Inc. |
| R1-2109907 | Discussion Summary #1 for Beam Management for new SCSs | Moderator (InterDigital, Inc.) |
| R1-2109964 | Enhancements for beam management to support NR above 52.6 GHz | LG Electronics |
| R1-2110024 | Beam Management for New SCSs | Apple |
| R1-2110112 | Beam management for NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2110175 | Beam managment for new SCS | Qualcomm Incorporated |
| R1-2110524 | Discussion Summary #2 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2110525 | Discussion Summary #3 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2110632 | Discussion Summary #4 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2110633 | Discussion Summary #5 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| 8.2.5 | PDSCH/PUSCH enhancements | |
| R1-2108771 | PDSCH/PUSCH enhancements for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2108786 | Discussions on timeline, reference signal, and multi-PxSCH scheduling for 52.6GHz to 71GHz | FUTUREWEI |
| R1-2108904 | Discussion on PDSCH and PUSCH enhancements for above 52.6GHz | Spreadtrum Communications |
| R1-2108938 | Discussion on the data channel enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2108963 | Discussions on PDSCH/PUSCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2109033 | Considerations on multi-PDSCH/PUSCH with a single DCI and HARQ for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2109074 | Discussion on PDSCH/PUSCH enhancements | OPPO |
| R1-2109118 | Discussion on PDSCH enhancements supporting NR from 52.6GHz to 71 GHz | NEC |
| R1-2109163 | PT-RS enhancements for NR from 52.6GHz to 71GHz | Mitsubishi Electric RCE |
| R1-2109212 | PDSCH/PUSCH enhancements for up to 71GHz operation | CATT |
| R1-2109404 | PDSCH and PUSCH enhancements for NR 52.6-71GHz | Xiaomi |
| R1-2109438 | PDSCH-PUSCH Enhancements | Ericsson |
| R1-2109446 | PDSCH/PUSCH enhancements | Nokia, Nokia Shanghai Bell |
| R1-2109460 | Discussion on PDSCH/PUSCH enhancements for NR 52.6-71 GHz | Panasonic Corporation |
| R1-2109480 | PDSCH/PUSCH enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2109562 | Multi-PDSCH scheduling design for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2109602 | Discussion on PDSCH/PUSCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2109669 | PDSCH/PUSCH enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2109838 | Enhancements of PDSCH/PUSCH Scheduling for 52.6 GHz to 71 GHz Band | CEWiT |
| R1-2109901 | PDSCH/PUSCH scheduling enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2109908 | Discussion on PDSCH/PUSCH enhancements for supporting 52.6 GHz to 71 GHz Band | InterDigital, Inc. |
| R1-2109965 | PDSCH/PUSCH enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2109966 | Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2110025 | Discussion on PDSCH and PUSCH Enhancements for NR above 52.6 GHz | Apple |
| R1-2110113 | PDSCH design consideration for NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2110176 | PDSCH/PUSCH enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2110242 | Discussion on multiple PDSCHs scheduled by a DCI | ITRI |
| R1-2110321 | Discussion on multi-PDSCH/PUSCH scheduling for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2110398 | Summary of PDSCH/PUSCH enhancements (Bandwidth/Timeline/Reference signals) | Moderator (vivo) |
| R1-2110399 | Discussion summary #1 of [106bis-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2110512 | Discussion summary #2 of [106bis-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2110523 | Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2110640 | Summary #3 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| 8.2.6 | Channel access mechanism | |
| R1-2108772 | Channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2108787 | Channel access for shared spectrum for Beyond 52.6 GHz | FUTUREWEI |
| R1-2108905 | Discussion on channel access mechanism for above 52.6GHz | Spreadtrum Communications |
| R1-2108939 | Discussion on the channel access for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2108964 | Discussions on channel access mechanism for NR operation from 52.6GHz to 71 GHz | vivo |
| R1-2109034 | Considerations on channel access mechanism for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2109075 | Discussion on channel access mechanism | OPPO |
| R1-2109121 | Discussion on channel access mechanism supporting NR from 52.6 to 71GHz | NEC |
| R1-2109213 | Channel access mechanism for up to 71GHz operation | CATT |
| R1-2109268 | Channel access mechanism for NR in 60GHz unlicensed band operation | TCL Communication Ltd. |
| R1-2109345 | Views on channel access mechanism enhancements for 52.6-71 GHz | CAICT |
| R1-2109405 | Discussion on channel access mechanism for NR on 52.6-71 GHz | Xiaomi |
| R1-2109439 | Channel Access Mechanisms | Ericsson |
| R1-2109447 | Channel access mechanism | Nokia, Nokia Shanghai Bell |
| R1-2109481 | Channel access mechanism for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2109558 | On the channel access mechanisms for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2109603 | Discussion on channel access mechanism for extending NR up to 71 GHz | Intel Corporation |
| R1-2109670 | Channel access mechanism for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2109781 | Channel access mechanism for 60 GHz unlicensed spectrum | Sony |
| R1-2109902 | Channel access mechanisms for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2109909 | Discussion on channel access mechanisms | InterDigital, Inc. |
| R1-2109967 | Channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2110026 | Channel access mechanisms for unlicensed access above 52.6GHz | Apple |
| R1-2110115 | On Channel Access Mechanism for Supporting NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2110177 | Channel access mechanism for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2110243 | Discussion on multi-beam operation | ITRI |
| R1-2110247 | Channel access mechanisms for NR above 52 GHz | Charter Communications |
| R1-2110253 | Channel access for multi-beam operation | Panasonic |
| R1-2110322 | Discussion on channel access mechanism for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2110488 | Email discussion summary#1 for channel access of 52.6GHz to 71GHz band [106bis-e-NR-52-71GHz-07] | Moderator (Qualcomm) |
| R1-2110540 | Email discussion summary#2 for channel access of 52.6GHz to 71GHz band [106bis-e-NR-52-71GHz-07] | Moderator (Qualcomm) |
| 8.2.7 | Other | |
| R1-2108940 | Discussion on RRC parameters for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2108965 | Discussions on CSI-RS related issues for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2109214 | Some issues on SPS for one DCI scheduling multiple PDSCHs case | CATT |
| R1-2109440 | NR channelization for the 57 – 71 GHz band | Ericsson |
| R1-2109448 | Simulation results | Nokia, Nokia Shanghai Bell |
| R1-2109756 | LLS results for enhancement reference signals | Huawei, HiSilicon |
| R1-2109968 | Link level evaluation results for NR FR2-2 PTRS design | LG Electronics |
| 8.3 | Enhanced Industrial Internet of Things (IoT) and URLLC | |
| R1-2110563 | Summary of [106bis-e-R17-RRC-IIoT-URLLC] Email discussion on Rel-17 RRC parameters for IIoT and URLLC | Moderator (Nokia) |
| R1-2110670 | List of agreements of Rel-17 URLLC/IIoT WI (post RAN1#106bis-e) | WI rapporteur (Nokia) |
| 8.3.1.1 | UE feedback enhancements for HARQ-ACK | |
| R1-2108726 | UE feedback enhancements for HARQ-ACK | Huawei, HiSilicon |
| R1-2108829 | HARQ-ACK Enhancements for IIoT/URLLC | Ericsson |
| R1-2108840 | Discussion on HARQ-ACK enhancements for eURLLC | ZTE |
| R1-2108906 | Discussion on HARQ-ACK feedback enhancements for Rel-17 URLLC | Spreadtrum Communications |
| R1-2108966 | HARQ-ACK enhancements for Rel-17 URLLC | vivo |
| R1-2109093 | HARQ-ACK enhancements for Rel-17 URLLC/IIoT | OPPO |
| R1-2109131 | UE feedback enhancements for HARQ-ACK | NEC |
| R1-2109159 | HARQ-ACK Feedback Enhancements for URLLC/IIoT | Nokia, Nokia Shanghai Bell |
| R1-2109162 | Moderator summary #1 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2109215 | UE feedback enhancements for HARQ-ACK | CATT |
| R1-2109256 | Discussion on some remaining issues for UE HARQ-ACK feedback enhancements | China Telecom |
| R1-2109277 | Discussion on UE feeback enhancements for HARQ-ACK | CMCC |
| R1-2109342 | UE feedback enhancements for HARQ-ACK | CAICT |
| R1-2109354 | UE feedback enhancements for HARQ-ACK | TCL Communication Ltd. |
| R1-2109406 | UE feedback enhancements for HARQ-ACK | Xiaomi |
| R1-2109482 | On HARQ-ACK reporting enhancements | Samsung |
| R1-2109575 | On UE feedback enhancements for HARQ-ACK | MediaTek Inc. |
| R1-2109604 | Remaining issues of enhanced HARQ-ACK feedback procedures | Intel Corporation |
| R1-2109671 | Discussion on HARQ-ACK feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2109782 | Considerations on HARQ-ACK enhancements for URLLC | Sony |
| R1-2109809 | UE feedback enhancements for HARQ-ACK | ETRI |
| R1-2109821 | Discussion on UE feedback enhancements for HARQ-ACK | Panasonic |
| R1-2109822 | Discussion on UE feedback enhancements for HARQ-ACK | FGI, Asia Pacific Telecom |
| R1-2109893 | HARQ enhancements for IIoT and URLLC | InterDigital, Inc. |
| R1-2109940 | HARQ-ACK feedback enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2109970 | Discussion on UE feedback enhancement for HARQ-ACK | LG Electronics |
| R1-2110027 | Rel-17 URLLC UE feedback enhancements for HARQ-ACK | Apple |
| R1-2110178 | HARQ-ACK enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2110244 | On the UE feedback enhancements for HARQ-ACK | ITRI |
| R1-2110287 | Discussion on PUCCH carrier switch for HARQ-ACK enhancement | ASUSTeK |
| R1-2110527 | Moderator summary #2 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2110561 | Moderator summary #3 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2110562 | Final moderator summary on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| 8.3.1.2 | CSI feedback enhancements | |
| R1-2108727 | CSI feedback enhancements | Huawei, HiSilicon |
| R1-2108830 | CSI Feedback Enhancements for IIoT/URLLC | Ericsson |
| R1-2108841 | Discussion on CSI feedback enhancements for eURLLC | ZTE |
| R1-2108967 | CSI feedback enhancements for Rel-17 URLLC | vivo |
| R1-2109094 | CSI feedback enhancements for URLLC | OPPO |
| R1-2109216 | CSI feedback enhancements | CATT |
| R1-2109259 | Discussion on CSI Feedback Enhancements | Quectel, Langbo |
| R1-2109278 | Discussion on CSI feeback enhancements for URLLC | CMCC |
| R1-2109605 | Remaining issues of enhanced sub-band CQI indication granularity | Intel Corporation |
| R1-2109672 | Discussion on CSI feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2109729 | CSI feedback enhancements | InterDigital, Inc. |
| R1-2109783 | Remaining issues in 4 bits sub-band CQI reporting | Sony |
| R1-2109910 | Feature lead summary#1 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2109941 | CSI feedback enhancements for URLLC/IIoT | Lenovo, Motorola Mobility |
| R1-2109971 | Discussion on CSI feedback enhancements for URLLC | LG Electronics |
| R1-2110028 | Rel-17 URLLC UE feedback enhancement for CSI | Apple |
| R1-2110179 | CSI enhancement for IOT and URLLC | Qualcomm Incorporated, Samsung |
| R1-2110303 | CSI feedback enhancements for URLLC/IIoT use cases | Nokia, Nokia Shanghai Bell |
| R1-2110395 | Discussion on CSI feedback enhancements for eURLLC | ZTE |
| R1-2110509 | Feature lead summary#2 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| R1-2110551 | Feature lead summary #3 on CSI feedback enhancements for enhanced URLLC/IIoT | Moderator (InterDigital, Inc.) |
| 8.3.2 | Enhancements for unlicensed band URLLC/IIoT | |
| R1-2108729 | Uplink enhancements for URLLC in unlicensed controlled environments | Huawei, HiSilicon |
| R1-2108788 | UE initiated COT for semi-static channel access | FUTUREWEI |
| R1-2108831 | Enhancements for IIoT/URLLC on Unlicensed Band | Ericsson |
| R1-2108842 | Discussion on unlicensed band URLLC/IIoT | ZTE |
| R1-2108907 | Discussion on enhancements for unlicensed band URLLCIIoT | Spreadtrum Communications |
| R1-2108968 | Enhancements for unlicensed band URLLC/IIoT | vivo |
| R1-2109095 | Enhancements for unlicensed band URLLC/IIoT | OPPO |
| R1-2109138 | UL enhancements for IIoT/URLLC in unlicensed controlled environment | Nokia, Nokia Shanghai Bell |
| R1-2109217 | Discussion on remaining issues on enhancements for unlicensed band URLLC/IIoT | CATT |
| R1-2109356 | Enhancements for unlicensed band URLLC/IIoT | NEC |
| R1-2109407 | Enhancement for unlicensed band URLLC IIoT | Xiaomi |
| R1-2109453 | Enhancements for unlicensed band URLLC/IIoT | Panasonic Corporation |
| R1-2109483 | Enhancements for unlicensed band URLLC/IIoT | Samsung |
| R1-2109576 | On the enhancements for unlicensed band URLLC/IIoT | MediaTek Inc. |
| R1-2109606 | Further Details for Enabling URLLC/IIOT in Unlicensed Band | Intel Corporation |
| R1-2109673 | Discussion on enhancements for unlicensed band URLLC | NTT DOCOMO, INC. |
| R1-2109784 | Considerations on unlicensed URLLC | Sony |
| R1-2109810 | Enhancements for unlicensed band URLLC/IIoT | ETRI |
| R1-2109894 | Enhancements for unlicensed band URLLC/IIoT | InterDigital, Inc. |
| R1-2109942 | Enhancements for unlicensed band URLLC/IIoT | Lenovo, Motorola Mobility |
| R1-2109972 | Discussion on unlicensed band URLLC/IIOT | LG Electronics |
| R1-2109994 | Enhancements for unlicensed band URLLC/IIoT | Sharp |
| R1-2110029 | URLLC uplink enhancements for unlicensed spectrum | Apple |
| R1-2110180 | Uplink enhancements for URLLC in unlicensed controlled environments | Qualcomm Incorporated |
| R1-2110323 | Discussion on enhancement for unlicensed URLLC/IIoT | WILUS Inc. |
| R1-2110396 | Discussion on unlicensed band URLLC/IIoT | ZTE |
| R1-2110423 | Summary#1 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2110424 | Summary#2 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2110425 | Summary#3 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2110426 | Summary#4 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2110427 | Summary#5 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2110653 | Summary#6 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| 8.3.3 | Intra-UE Multiplexing/Prioritization | |
| R1-2108728 | Intra-UE multiplexing enhancements | Huawei, HiSilicon |
| R1-2108832 | Intra-UE Multiplexing/Prioritization Enhancements for IIoT/URLLC | Ericsson |
| R1-2108843 | Discussion on enhanced intra-UE multiplexing | ZTE |
| R1-2108908 | Discussion on intra-UE multiplexing/prioritization | Spreadtrum Communications |
| R1-2108969 | Intra-UE Multiplexing/Prioritization for Rel-17 URLLC | vivo |
| R1-2109096 | Enhancements on intra-UE multiplexing/prioritization | OPPO |
| R1-2109132 | Discussion on Intra-UE prioritization and multiplexing | NEC |
| R1-2109160 | On UL intra-UE prioritization and multiplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2109218 | Intra-UE multiplexing and prioritization | CATT |
| R1-2109260 | Discussion on Intra-UE Multiplexing/Prioritization | Quectel, Langbo |
| R1-2109355 | Intra-UE multiplexing and prioritization | TCL Communication Ltd. |
| R1-2109408 | Intra-UE multiplexing prioritization for URLLC IIoT | Xiaomi |
| R1-2109454 | Discussion on Intra-UE multiplexing of different priority | Panasonic Corporation |
| R1-2109484 | Uplink intra-UE multiplexing and prioritization | Samsung |
| R1-2109577 | Methods for intra-UE multiplexing and prioritization | MediaTek Inc. |
| R1-2109607 | Further details of intra-UE uplink channel multiplexing and prioritization | Intel Corporation |
| R1-2109674 | Discussion on intra-UE multiplexing/prioritization for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2109730 | Intra-UE multiplexing and prioritization | InterDigital, Inc. |
| R1-2109785 | Considerations on intra-UE UL multiplexing | Sony |
| R1-2109811 | Intra-UE Multiplexing/Prioritization | ETRI |
| R1-2109943 | Intra-UE multiplexing enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2109973 | Discussion on Intra-UE multiplexing/prioritization | LG Electronics |
| R1-2109995 | Enhancements of channel collision resolution and intra-UE UCI multiplexing on PUCCH and PUSCH | Sharp |
| R1-2110030 | Rel-17 URLLC intra-UE multiplexing/prioritization | Apple |
| R1-2110181 | Intra-UE multiplexing and prioritization for IOT and URLLC | Qualcomm Incorporated |
| R1-2110245 | Discussion on intra-UE multiplexing and prioritization | ITRI |
| R1-2110324 | Discussion on intra-UE multiplexing/prioritization for URLLC/IIoT | WILUS Inc. |
| R1-2110416 | Rel-17 URLLC intra-UE multiplexing/prioritization | Apple |
| R1-2110463 | Summary#1 of email thread [106bis-e-NR-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2110472 | Summary#2 of email thread [106bis-e-NR-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2110510 | Further discussion on UCI multiplexing and power control in Rel-17 URLLC | Apple |
| R1-2110547 | Summary#3 of email thread [106bis-e-NR-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2110636 | Summary#4 of email thread [106bis-e-NR-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| 8.3.4 | Other | |
| R1-2108833 | Propagation Delay Compensation Enhancements for Time Synchronization | Ericsson |
| R1-2108844 | Discussion on propagation delay compensation enhancements | ZTE |
| R1-2108970 | Discussion on propagation delay compensation enhancements | vivo |
| R1-2109097 | Enhancement for support of time synchronization | OPPO |
| R1-2109161 | Discussion on enhancements for propagation delay compensation | Nokia, Nokia Shanghai Bell |
| R1-2109219 | Discussion on propagation delay compensation enhancements | CATT |
| R1-2109485 | Discussion for propagation delay compensation enhancements | Samsung |
| R1-2109608 | Remaining issues on propagation delay compensation | Intel Corporation |
| R1-2109743 | Enhancements for support of time synchronization | Huawei, HiSilicon |
| R1-2109974 | Discussion on propagation delay compensation enhancements | LG Electronics |
| R1-2110182 | Enhancements for support of time synchronization for enhanced IIoT and URLLC | Qualcomm Incorporated |
| R1-2110397 | Discussion on propagation delay compensation enhancements | ZTE |
| R1-2110473 | Feature lead summary#1 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2110474 | Feature lead summary#2 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2110558 | Feature lead summary#3 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2110559 | Feature lead summary#4 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2110594 | Draft LS on propagation delay compensation | Huawei |
| R1-2110647 | LS on propagation delay compensation | RAN1, Huawei |
| R1-2110651 | Final feature lead summary on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2110700 | Happy Birthday Patrick | RAN1 |
| 8.4 | Solutions for NR to support non-terrestrial networks (NTN) | |
| R1-2110374 | Updated NR_NTN_solutions work plan | Thales |
| R1-2110613 | Session notes for 8.4 (Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Ericsson) |
| R1-2110624 | Summary of [106bis-e-R17-RRC-NR-NTN] Email discussion on Rel-17 RRC parameters for NR to support NTN | Moderator (Thales) |
| R1-2110685 | 3GPP TSG-RAN WG1 Agreements under 8.4 up to eMeeting RAN1#106-bis-e | WI rapporteur (Thales) |
| 8.4.1 | Timing relationship enhancements | |
| R1-2108747 | Discussion on timing relationship enhancements for NTN | Huawei, HiSilicon |
| R1-2108909 | Discussion on timing relationship enhancements for NTN | Spreadtrum Communications |
| R1-2108971 | Discussion on timing relationship enhancements for NR-NTN | vivo |
| R1-2109025 | Timing relationship enhancements for NTN | Zhejiang Lab |
| R1-2109076 | Discussion on timing relationship enhancement | OPPO |
| R1-2109164 | Further discussion on timing relation aspects for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2109168 | Timing relationship enhancements for NR-NTN | MediaTek Inc. |
| R1-2109220 | Further discussion on timing relationship enhancements for NTN | CATT |
| R1-2109279 | Discussion on timing relationship enhancements for NTN | CMCC |
| R1-2109323 | Discussion on NTN timing relationship | Lenovo, Motorola Mobility |
| R1-2109343 | Timing relationship enhancements to support NTN | CAICT |
| R1-2109357 | Discussion on timing relationship enhancements for NTN | NEC |
| R1-2109409 | Discussion on the timing relationship enhancement for NTN | Xiaomi |
| R1-2109486 | Timing relationship enhancements for NTN | Samsung |
| R1-2109609 | On timing relationship enhancements for NTN | Intel Corporation |
| R1-2109675 | Discussion on timing relationship enhancements for NTN | NTT DOCOMO, INC. |
| R1-2109763 | Discussion on timing relationship enhancement for NTN | Baicells |
| R1-2109786 | Calculation and application of timing relationship offsets | Sony |
| R1-2109825 | Timing relationship enhancements in NTN | FGI, Asia Pacific Telecom, III |
| R1-2109843 | Discussion on timing relationship for NR-NTN | ZTE |
| R1-2109865 | Timing relationship for NTN | Panasonic Corporation |
| R1-2109878 | Timing relationship enhancement for NTN | InterDigital, Inc. |
| R1-2109927 | On timing relationship enhancements for NTN | Ericsson |
| R1-2109932 | Timing relationship enhancements for NTN | ITL |
| R1-2110031 | Discussion on Timing Relationship Enhancements for NR NTN | Apple |
| R1-2110084 | Discussions on timing relationship enhancements in NTN | LG Electronics |
| R1-2110183 | Enhancements for Timing Relationship for NTN | Qualcomm Incorporated |
| R1-2110290 | Discussion on Timing Relationship Enhancements for NTN | Fraunhofer IIS - Fraunhofer HHI |
| R1-2110387 | Feature lead summary#1 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2110487 | Feature lead summary#2 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2110505 | Feature lead summary#3 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2110541 | Feature lead summary#4 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2110577 | Feature lead summary#5 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2110641 | Feature lead summary#6 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2110663 | LS on UE TA reporting | RAN1, Ericsson |
| 8.4.2 | Enhancements on UL time and frequency synchronization | |
| R1-2108720 | Considerations on UL timing and frequency synchronization in NTN | THALES |
| R1-2108721 | FL Summary #1 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2108722 | FL Summary #2 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2108748 | Discussion on UL time and frequency synchronization enhancement for NTN | Huawei, HiSilicon |
| R1-2108779 | FL Summary #3 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2108780 | FL Summary #4 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2108781 | FL Summary #5 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2108910 | Discussion on enhancements on UL time and frequency synchronization for NTN | Spreadtrum Communications |
| R1-2108972 | Discussion on UL time and frequency synchronization enhancements for NR-NTN | vivo |
| R1-2109077 | Discussion on UL time and frequency synchronization | OPPO |
| R1-2109165 | Further discussion on synchronization aspects for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2109169 | Enhancements on UL Time and Frequency Synchronisation for NR-NTN | MediaTek Inc. |
| R1-2109221 | Further discussion on UL time and frequency synchronization enhancement for NTN | CATT |
| R1-2109280 | Enhancements on UL time and frequency synchronization for NTN | CMCC |
| R1-2109324 | Discussion on NTN uplink time synchronization | Lenovo, Motorola Mobility |
| R1-2109358 | Discussion on UL time synchronization for NR NTN | NEC |
| R1-2109410 | Discussion on UL time and frequency synchronization for NTN | Xiaomi |
| R1-2109487 | Enhancements on UL time and frequency synchronization for NTN | Samsung |
| R1-2109610 | On UL synchronization for NTN | Intel Corporation |
| R1-2109676 | Discussion on UL time and frequency synchronization enhancements for NTN | NTT DOCOMO, INC. |
| R1-2109764 | Discussion on UL time and frequency synchronization enhancement for NTN | Baicells |
| R1-2109787 | Considerations on UL time synchronisation | Sony |
| R1-2109826 | UL time and frequency synchronization in NTN | FGI, Asia Pacific Telecom, III, ITRI |
| R1-2109844 | Discussion on UL synchronization for NR-NTN | ZTE |
| R1-2109858 | Enhancements on UL time and frequency synchronization | PANASONIC R&D Center Germany |
| R1-2109879 | UL time/frequency synchronization for NTN | InterDigital, Inc. |
| R1-2109928 | On UL time and frequency synchronization enhancements for NTN | Ericsson |
| R1-2110032 | Discussion on Uplink Time and Frequency Synchronization for NR NTN | Apple |
| R1-2110085 | Discussions on UL time and frequency synchronization enhancements in NTN | LG Electronics |
| R1-2110184 | UL time and frequency synchronization for NTN | Qualcomm Incorporated |
| R1-2110292 | Discussion on UL Time Synchronization for NTN | Fraunhofer IIS - Fraunhofer HHI |
| R1-2110602 | FL Summary #6 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2110603 | Draft LS on Combination of open and closed loop TA control in NTN | Moderator (Thales) |
| R1-2110604 | LS on Combination of open and closed loop TA control in NTN | RAN1, Thales |
| 8.4.3 | Enhancements on HARQ | |
| R1-2108749 | Discussion on HARQ enhancement for NTN | Huawei, HiSilicon |
| R1-2108911 | Discussion on enhancements on HARQ for NTN | Spreadtrum Communications |
| R1-2108973 | Discussion on HARQ enhancements for NR-NTN | vivo |
| R1-2109078 | Discussion on HARQ enhancements | OPPO |
| R1-2109166 | Further discussion of aspects related to HARQ for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2109170 | Enhancements on HARQ for NR NTN | MediaTek Inc. |
| R1-2109222 | Further discussion on HARQ operation enhancement for NTN | CATT |
| R1-2109281 | Enhancements on HARQ for NTN | CMCC |
| R1-2109344 | Enhancements on HARQ to support NTN | CAICT |
| R1-2109359 | Discussion on HARQ enhancements for NR NTN | NEC |
| R1-2109411 | Discussion on the HARQ enhancement for NTN | Xiaomi |
| R1-2109488 | Enhancements on HARQ for NTN | Samsung |
| R1-2109677 | Discussion on HARQ enhancements for NR NTN | NTT DOCOMO, INC. |
| R1-2109765 | Discussion on HARQ enhancement for NTN | Baicells |
| R1-2109788 | Enhancements on HARQ for NTN | Sony |
| R1-2109812 | Discussion on HARQ Enhancements for NTN | ETRI |
| R1-2109827 | Enhancements on HARQ in NTN | FGI, Asia Pacific Telecom, III |
| R1-2109845 | Discussion on HARQ for NR-NTN | ZTE |
| R1-2109868 | HARQ enhancement for NTN | Panasonic Corporation |
| R1-2109880 | HARQ enhancement for NTN | InterDigital, Inc. |
| R1-2109929 | On HARQ enhancements for NTN | Ericsson |
| R1-2109933 | Discussion on HARQ enhancements for NTN | ITL |
| R1-2110033 | Discussion on HARQ Enhancements for NR NTN | Apple |
| R1-2110086 | Discussions on HARQ enhancements in NTN | LG Electronics |
| R1-2110185 | Enhancements for HARQ for NTN | Qualcomm Incorporated |
| R1-2110471 | Summary#1 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2110532 | Summary#2 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| R1-2110546 | Summary#3 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE) |
| 8.4.4 | Other | |
| R1-2108912 | Discussion on beam management and other aspects for NTN | Spreadtrum Communications |
| R1-2108974 | Discussion on other aspects for NR-NTN | vivo |
| R1-2109079 | Discussion on beam management | OPPO |
| R1-2109167 | Further discussion on remaining aspects for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2109223 | Beam management and other aspects for NTN | CATT |
| R1-2109282 | Other Aspects for NTN | CMCC |
| R1-2109325 | Discussion on other aspects for NTN | Lenovo, Motorola Mobility |
| R1-2109360 | Remaining issues for NR NTN | NEC |
| R1-2109412 | Discussion on other design aspects for NTN | Xiaomi |
| R1-2109489 | Remaining issues for NTN | Samsung |
| R1-2109678 | Discussion on other aspects for NR NTN | NTT DOCOMO, INC. |
| R1-2109749 | Discussion on other design aspects for NTN | Huawei, HiSilicon |
| R1-2109766 | Discussion on beam management and other consideration for NTN | Baicells |
| R1-2109789 | Discussion on beam management and polarization for NTN | Sony |
| R1-2109828 | Other aspects of NR-NTN | FGI, Asia Pacific Telecom, III, ITRI |
| R1-2109846 | Discussion on additional enhancement for NR-NTN | ZTE |
| R1-2109877 | Network Verified UE Location in Non-Terrestrial Networks | Fraunhofer IIS, Fraunhofer HHI, Thales |
| R1-2109881 | On beam management for NTN | InterDigital, Inc. |
| R1-2109892 | Considerations on NTN with Transparent Payload | III |
| R1-2109930 | On other enhancements for NTN | Ericsson |
| R1-2110034 | Discussion on Other Aspects of NR NTN | Apple |
| R1-2110087 | Discussions on other aspects of NTN | LG Electronics |
| R1-2110186 | BWP operation and other issues for NTN | Qualcomm Incorporated |
| R1-2110259 | Beam management and polarization signaling for NTN | Panasonic |
| R1-2110489 | Summary of the discussions on other enhancements | Moderator (OPPO) |
| R1-2110570 | Summary#2 of the discussions on other enhancements | Moderator (OPPO) |
| 8.5 | NR Positioning Enhancements | |
| R1-2110388 | FL Summary for Rel-17 RRC parameters for positioning enhancement | Moderator (CATT) |
| R1-2110389 | FL Summary #2 for Rel-17 RRC parameters for positioning enhancement | Moderator (CATT) |
| R1-2110390 | FL Summary #3 for Rel-17 RRC parameters for positioning enhancement | Moderator (CATT) |
| R1-2110614 | Session notes for 8.5 (NR Positioning Enhancements) | Ad-Hoc Chair (Ericsson) |
| R1-2110667 | Summary of RAN1 agreements for Rel-17 NR Positioning Enhancements | WI rapporteur (CATT) |
| R1-2110690 | Summary of RAN1 agreements for Rel-17 NR Positioning Enhancements | WI rapporteur (CATT) |
| 8.5.1 | Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | |
| R1-2108730 | Remaining issues of mitigating Rx/Tx timing error | Huawei, HiSilicon |
| R1-2108878 | Positioning accuracy improvement by mitigating timing delay | ZTE |
| R1-2108975 | Discussion on potential enhancements for RX/TX timing delay mitigating | vivo |
| R1-2109051 | Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | OPPO |
| R1-2109224 | Further discussion on mitigating UE and gNB Rx/Tx timing errors | CATT |
| R1-2109283 | Discussion on mitigation of gNB/UE Rx/Tx timing errors | CMCC |
| R1-2109363 | Views on mitigating UE and gNB Rx/Tx timing errors | Nokia, Nokia Shanghai Bell |
| R1-2109490 | Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Samsung |
| R1-2109611 | Mitigation of UE and gNB RX/TX Timing Errors | Intel Corporation |
| R1-2109679 | Discussion on mitigating UE and gNB Rx/Tx timing delays | NTT DOCOMO, INC. |
| R1-2109790 | Discussion on mitigating Rx/Tx timing delays | Sony |
| R1-2110035 | Positioning accuracy enhancements under timing errors | Apple |
| R1-2110088 | Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays | LG Electronics |
| R1-2110133 | Discussion on accuracy improvements by mitigating timing delays | InterDigital, Inc. |
| R1-2110187 | Remaining Issues for Timing Error Mitigation for improved Accuracy | Qualcomm Incorporated |
| R1-2110254 | Mitigation of RX/TX timing delays for higher accuracy | MediaTek Inc. |
| R1-2110298 | Considerations for mitigation of Tx/Rx Delays | Lenovo, Motorola Mobility |
| R1-2110349 | Techniques mitigating Rx/Tx timing delays | Ericsson |
| R1-2110391 | FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2110392 | FL Summary #2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2110393 | FL Summary #3 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2110579 | FL Summary #4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| 8.5.2 | Accuracy improvements for UL-AoA positioning solutions | |
| R1-2108731 | Remaining issues of UL AoA enhancements | Huawei, HiSilicon |
| R1-2108879 | Accuracy improvement for UL-AoA positioning solutions | ZTE |
| R1-2108976 | Discussion on potential enhancements for UL-AoA method | vivo |
| R1-2109052 | Enhancements for UL AoA Positioning | OPPO |
| R1-2109225 | Further discussion on enhancements for UL-AoA positioning method | CATT |
| R1-2109364 | Views on enhancing UL AoA | Nokia, Nokia Shanghai Bell |
| R1-2109491 | Discussion on accuracy improvements for UL-AoA positioning solutions | Samsung |
| R1-2109612 | Remaining Aspects of NR Positioning UL-AoA Enhancements | Intel Corporation |
| R1-2109680 | Discussion on UL-AoA positioning enhancements | NTT DOCOMO, INC. |
| R1-2109791 | Considerations on enhancements for UL-AoA | Sony |
| R1-2109863 | TRP Rx-ARP information reporting | Fraunhofer IIS, Fraunhofer HHI |
| R1-2110036 | Positioning Accuracy enhancements for UL-AoA | Apple |
| R1-2110089 | Discussion on accuracy improvement for UL-AoA positioning | LG Electronics |
| R1-2110134 | Enhancements for UL-AoA positioning solutions | InterDigital, Inc. |
| R1-2110188 | Potential Enhancements on UL-AOA positioning | Qualcomm Incorporated |
| R1-2110345 | Discussion on enhancements for UL AoA positioning | CEWiT |
| R1-2110350 | Enhancements of UL-AoA positioning solutions | Ericsson |
| R1-2110453 | Feature Lead Summary#1 for E-mail Discussion [106bis-e-NR-ePos-02] | Moderator (Intel Corporation) |
| R1-2110454 | Feature Lead Summary#2 for E-mail Discussion [106bis-e-NR-ePos-02] | Moderator (Intel Corporation) |
| R1-2110455 | Feature Lead Summary#3 for E-mail Discussion [106bis-e-NR-ePos-02] | Moderator (Intel Corporation) |
| 8.5.3 | Accuracy improvements for DL-AoD positioning solutions | |
| R1-2108732 | Remaining issues of DL AoD enhancements | Huawei, HiSilicon |
| R1-2108880 | Accuracy improvement for DL-AoD positioning solutions | ZTE |
| R1-2108977 | Discussion on potential enhancements for DL-AoD method | vivo |
| R1-2109053 | Enhancements for DL-AoD positioning | OPPO |
| R1-2109226 | Further discussion on enhancements for DL-AoD positioning method | CATT |
| R1-2109284 | Discussion on DL-AoD enhancements | CMCC |
| R1-2109346 | Discussion on enhancements for DL-AoD positioning | CAICT |
| R1-2109365 | Views on enhancing DL AoD | Nokia, Nokia Shanghai Bell |
| R1-2109413 | Accuracy improvements for DL-AoD positioning solutions | Xiaomi |
| R1-2109492 | Discussion on accuracy improvements for DL-AoD positioning solutions | Samsung |
| R1-2109613 | Solutions for NR Positioning DL-AoD Enhancements | Intel Corporation |
| R1-2109681 | Discussion on DL-AoD positioning enhancements | NTT DOCOMO, INC. |
| R1-2109792 | Considerations on enhancements for DL-AoD | Sony |
| R1-2109864 | DL-AoD positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2110037 | Positioning Accuracy enhancements for DL-AoD | Apple |
| R1-2110090 | Discussion on accuracy improvement for DL-AoD positioning | LG Electronics |
| R1-2110148 | Enhancements for DL-AoD positioning solutions | InterDigital, Inc. |
| R1-2110189 | Remaining Issues on Potential Enhancements for DL-AoD positioning | Qualcomm Incorporated |
| R1-2110256 | Accuracy enhancement for DL-AOD technique | MediaTek Inc. |
| R1-2110299 | Discussion on DL-AoD Positioning Enhancements | Lenovo, Motorola Mobility |
| R1-2110343 | Discussion on enhancements for DL-AoD positioning | CEWiT |
| R1-2110351 | Enhancements of DL-AoD positioning solutions | Ericsson |
| R1-2110460 | FL summary #1 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2110500 | FL summary #2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2110578 | FL summary #3 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2110625 | FL summary #4 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2110626 | [DRAFT] LS on definition of DL PRS path RSRP | Moderator (Ericsson) |
| R1-2110627 | LS on definition of DL PRS path RSRP | RAN1, Ericsson |
| 8.5.4 | Latency improvements for both DL and DL+UL positioning methods | |
| R1-2108733 | Enhancements to positioning latency improvements | Huawei, HiSilicon |
| R1-2108881 | Discussion on latency reduction for NR positioning | ZTE |
| R1-2108978 | Discussion on latency enhancement for NR positioning | vivo |
| R1-2109054 | Enhancements on Latency Reduction in NR Positioning | OPPO |
| R1-2109227 | Further discussion on latency reduction for NR positioning | CATT |
| R1-2109255 | Discussion on latency improvement for positioning methods | China Telecom |
| R1-2109285 | Discussion on latency improvement for positioning | CMCC |
| R1-2109366 | Views on PHY Latency Reductions | Nokia, Nokia Shanghai Bell |
| R1-2109414 | Latency improvements for both DL and DL+UL positioning method | Xiaomi |
| R1-2109493 | Discussion on latency improvements for both DL and DL+UL positioning methods | Samsung |
| R1-2109614 | Solutions for NR Positioning Latency Reduction | Intel Corporation |
| R1-2109682 | Discussion on latency improvements for both DL and DL+UL positioning methods | NTT DOCOMO, INC. |
| R1-2109793 | Considerations on latency improvements for NR positioning | Sony |
| R1-2110038 | Views on Rel-17 positioning latency reduction | Apple |
| R1-2110091 | Discussion on latency improvements for NR positioning | LG Electronics |
| R1-2110149 | Latency improvements for both DL and DL+UL positioning methods | InterDigital, Inc. |
| R1-2110190 | Remaining issues on Latency Improvements for Positioning | Qualcomm Incorporated |
| R1-2110257 | Physical latency improvement aspects | MediaTek Inc. |
| R1-2110300 | Enhancements for Positioning Latency Reduction | Lenovo, Motorola Mobility |
| R1-2110352 | Latency improvements for both DL and DL+UL positioning methods | Ericsson |
| R1-2110445 | FL summary #1 of 8.5.4 latency improvements for DL and DL+UL methods | Moderator (Huawei) |
| R1-2110446 | FL summary #2 of 8.5.4 latency improvements for DL and DL+UL methods | Moderator (Huawei) |
| R1-2110447 | FL summary #3 of 8.5.4 latency improvements for DL and DL+UL methods | Moderator (Huawei) |
| R1-2110605 | FL summary #4 of 8.5.4 latency improvements for DL and DL+UL methods | Moderator (Huawei) |
| 8.5.5 | Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | |
| R1-2108734 | Remaining issues of NLOS mitigation and multi-path reporting | Huawei, HiSilicon |
| R1-2108807 | NLOS Mitigation Enhancements | FUTUREWEI |
| R1-2108882 | Enhancements on NLOS and Multi-path mitigation for NR positioning | ZTE |
| R1-2108979 | Discussion on potential enhancements for multipath/NLOS mitigation | vivo |
| R1-2109055 | Discussion on multipath/NLOS mitigation for NR positioning | OPPO |
| R1-2109228 | Further discussion on information reporting from UE and gNB for multipath/NLOS mitigation | CATT |
| R1-2109367 | Views on LoS/NLoS Identification and Mitigation | Nokia, Nokia Shanghai Bell |
| R1-2109415 | Potential enhancements for multipath/NLOS mitigation | Xiaomi |
| R1-2109494 | Discussion on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | Samsung |
| R1-2109615 | Solutions for Mitigation of NLOS Problem for NR Positioning | Intel Corporation |
| R1-2109683 | Discussion on multipath/NLOS mitigation for NR positioning | NTT DOCOMO, INC. |
| R1-2109794 | Considerations on multipath/NLOS mitigation for NR positioning | Sony |
| R1-2109866 | Potential positioning enhancements for multipath/NLOS mitigation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2110039 | Views on potential enhancements for NLOS mitigation in Rel-17 positioning | Apple |
| R1-2110092 | Discussion on multipath/NLOS mitigation for positioning | LG Electronics |
| R1-2110150 | Discussion on multipath/NLOS mitigation for positioning | InterDigital, Inc. |
| R1-2110191 | Remaining Issues on Multipath Reporting in NR Positioning | Qualcomm Incorporated |
| R1-2110301 | Remaining issues for NLOS/Multipath Information Reporting | Lenovo, Motorola Mobility |
| R1-2110344 | Discussion on enhancements of multipath/NLOS reporting from UE and gNB | CEWiT |
| R1-2110353 | Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | Ericsson |
| R1-2110435 | Feature Lead Summary #1 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2110436 | Feature Lead Summary #2 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2110437 | Feature Lead Summary #3 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2110464 | Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | Ericsson |
| R1-2110609 | Feature Lead Summary #4 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| 8.5.6 | Other | |
| R1-2108883 | Discussion on items led by RAN2 for NR positioning | ZTE |
| R1-2108980 | Discussion on inactive state positioning and on-demand PRS | vivo |
| R1-2109056 | Discussion on positioning for UE in RRC_INACTIVE and on-demand PRS | OPPO |
| R1-2109229 | Further discussion on on-demand DL PRS and positioning for UEs in RRC_ INACTIVE state | CATT |
| R1-2109286 | Discussion on RAN2-led items for positioning | CMCC |
| R1-2109347 | Discussion on enhancements of INACTIVE mode positioning and on-demand PRS | CAICT |
| R1-2109368 | Additional views on Inactive Mode Positioning and on-demand PRS | Nokia, Nokia Shanghai Bell |
| R1-2109416 | On-demand PRS and positioning for UE in RRC_INACTIVE state | Xiaomi |
| R1-2109495 | Discussion on on demand positioning and positioning in inactive state | Samsung |
| R1-2109616 | Support of On-demand DL PRS and NR Positioning in RRC_INACTIVE State | Intel Corporation |
| R1-2109684 | Discussion on positioning for UEs in RRC_INACTIVE state | NTT DOCOMO, INC. |
| R1-2109744 | Discussion on INACTIVE state positioning and on-demand PRS | Huawei, HiSilicon |
| R1-2109795 | Considerations on on-demand PRS and positioning in RRC Inactive Mode | Sony |
| R1-2109867 | Considerations for on-Demand PRS and positioning in RRC_INACTIVE state | Fraunhofer IIS, Fraunhofer HHI |
| R1-2110093 | Discussion on other enhancements for positioning | LG Electronics |
| R1-2110151 | On-demand PRS and positioning during INACTIVE mode | InterDigital, Inc. |
| R1-2110192 | Remaining issues on enhancements Related to On Demand PRS And Positioning in RRC Inactive State | Qualcomm Incorporated |
| R1-2110261 | Potential physical layer impact to the RAN2-led topics | MediaTek Inc. |
| R1-2110302 | Discussion on On-Demand PRS and RRC_INACTIVE Positioning | Lenovo, Motorola Mobility |
| R1-2110354 | Further details for on-demand PRS reception and SRS in RRC_INACTIVE | Ericsson |
| R1-2110456 | Feature Lead Summary#1 for E-mail Discussion [106bis-e-NR-ePos-06] | Moderator (Intel Corporation) |
| R1-2110457 | Feature Lead Summary#2 for E-mail Discussion [106bis-e-NR-ePos-06] | Moderator (Intel Corporation) |
| R1-2110458 | Feature Lead Summary#3 for E-mail Discussion [106bis-e-NR-ePos-06] | Moderator (Intel Corporation) |
| R1-2110597 | Draft LS on support of SP-SRS for positioning by RRC_INACTIVE UEs | Moderator (Intel Corporation) |
| R1-2110598 | LS on support of SP-SRS for positioning by RRC_INACTIVE UEs | RAN1, Intel Corporation |
| R1-2110643 | Draft LS on DL PRS reception priority by RRC_INACTIVE Ues | Moderator (Intel) |
| R1-2110644 | LS on DL PRS reception priority by RRC_INACTIVE UEs | RAN1, Intel |
| 8.6 | Support of Reduced Capability NR Devices | |
| R1-2110383 | FL summary on RAN1 RRC parameter list for Rel-17 NR RedCap | Moderator (Ericsson) |
| R1-2110384 | Draft RAN1 RRC parameter list for Rel-17 NR RedCap | Moderator (Ericsson) |
| R1-2110385 | RAN1 agreements for Rel-17 NR RedCap | Rapporteur (Ericsson) |
| R1-2110615 | Session notes for 8.6 (Support of Reduced Capability NR Devices) | Ad-hoc Chair (CMCC) |
| R1-2110669 | RAN1 agreements for Rel-17 NR RedCap | Rapporteur (Ericsson) |
| 8.6.1.1 | Aspects related to reduced maximum UE bandwidth | |
| R1-2108753 | Reduced maximum UE bandwidth | Huawei, HiSilicon |
| R1-2108802 | Further discussion on Bandwidth Reduction for RedCap UEs | FUTUREWEI |
| R1-2108820 | Reduced maximum UE bandwidth for RedCap | Ericsson |
| R1-2108913 | Discussion on aspects related to reduced maximum UE bandwidth | Spreadtrum Communications |
| R1-2108981 | Discussion on reduced maximum UE bandwidth | vivo, Guangdong Genius |
| R1-2109082 | Discussion on reduced UE bandwidth | OPPO |
| R1-2109230 | Discussion on reduced maximum UE bandwidth | CATT |
| R1-2109287 | Discussion on reduced maximum UE bandwidth | CMCC |
| R1-2109310 | Bandwidth Reduction for Reduced Capability Devices | Nokia, Nokia Shanghai Bell |
| R1-2109326 | Reduced maximum UE bandwidth for RedCap | Lenovo, Motorola Mobility |
| R1-2109332 | Bandwidth reduction for reduced capability NR devices | ZTE, Sanechips |
| R1-2109417 | Discussion on the remaining issues of reduced UE bandwidth for RedCap | Xiaomi |
| R1-2109496 | UE complexity reduction | Samsung |
| R1-2109573 | On reduced maximum bandwidth for RedCap UEs | MediaTek Inc. |
| R1-2109617 | Support of reduced max UE BW for RedCap | Intel Corporation |
| R1-2109685 | Discussion on reduced maximum UE bandwidth for RedCap | NTT DOCOMO, INC. |
| R1-2109759 | Discussion on reduced maximum UE bandwidth for RedCap | NEC |
| R1-2109796 | Discussion on reduced maximum UE bandwidth for RedCap | Sony |
| R1-2109841 | Aspects related to reduced maximum UE bandwidth for RedCap | Panasonic Corporation |
| R1-2109948 | Discussion on reduced maximum bandwidth for RedCap UEs | InterDigital, Inc. |
| R1-2109975 | Aspects related to the reduced maximum UE bandwidth of RedCap | LG Electronics |
| R1-2109996 | Discussion on reduced maximum UE bandwidth | Sharp |
| R1-2110040 | Reduced maximum UE bandwidth for Redcap | Apple |
| R1-2110105 | Discussion on aspects related to reduced maximum UE bandwidth | ASUSTeK |
| R1-2110193 | BW Reduction for RedCap UE | Qualcomm Incorporated |
| R1-2110279 | On aspects related to reduced maximum UE BW | Nordic Semiconductor ASA |
| R1-2110314 | Reduced maximum UE bandwidth for RedCap | DENSO CORPORATION |
| R1-2110377 | FL summary #1 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2110378 | FL summary #2 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2110379 | FL summary #3 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2110380 | FL summary #4 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2110381 | FL summary #5 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2110481 | Support of reduced max UE BW for RedCap | Intel Corporation |
| R1-2110599 | Draft LS on use of NCD-SSB instead of CD-SSB for RedCap UE | Moderator (Ericsson) |
| R1-2110600 | LS on use of NCD-SSB instead of CD-SSB for RedCap UE | RAN1, Ericsson |
| 8.6.1.2 | Aspects related to duplex operation | |
| R1-2108754 | Duplex operation for RedCap | Huawei, HiSilicon |
| R1-2108821 | Duplex operation for RedCap | Ericsson |
| R1-2108914 | Discussion on duplex operation for RedCap | Spreadtrum Communications |
| R1-2108982 | Discussion on RedCap half-duplex operation | vivo, Guangdong Genius |
| R1-2109083 | On half-duplex operation | OPPO |
| R1-2109231 | Discussion on HD-FDD operation | CATT |
| R1-2109253 | Discussion on duplex operation for RedCap | China Telecom |
| R1-2109288 | Discussion on collision handling of HD-FDD operation | CMCC |
| R1-2109311 | Half-Duplex Operation for Reduced Capability Devices | Nokia, Nokia Shanghai Bell |
| R1-2109333 | HD-FDD for reduced capability NR devices | ZTE, Sanechips |
| R1-2109418 | Discussion on the remaining issues of HD-FDD for RedCap | Xiaomi |
| R1-2109451 | Discussion on aspects related to duplex operation | Potevio Company Limited |
| R1-2109497 | HD-FDD Operation for RedCap UEs | Samsung |
| R1-2109574 | On half duplex operation for RedCap UEs | MediaTek Inc. |
| R1-2109618 | Support of HD-FDD for RedCap | Intel Corporation |
| R1-2109686 | Discussion on duplex operation for RedCap | NTT DOCOMO, INC. |
| R1-2109842 | Aspects related to duplex operation for RedCap | Panasonic Corporation |
| R1-2109949 | Duplex operation for RedCap UEs | InterDigital, Inc. |
| R1-2109976 | Aspects related to the duplex operation of RedCap | LG Electronics |
| R1-2109997 | Discussion on duplex operation for redcap UEs | Sharp |
| R1-2110041 | Duplex Operation for Redcap | Apple |
| R1-2110108 | Discussion on aspects related to duplex operation | ASUSTeK |
| R1-2110194 | Type-A HD-FDD Operation for RedCap UE | Qualcomm Incorporated |
| R1-2110281 | On aspects related to duplex operation | Nordic Semiconductor ASA |
| R1-2110325 | Discussion on duplex operation for RedCap UE | WILUS Inc. |
| R1-2110431 | FL summary #1 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| R1-2110432 | FL summary #2 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| R1-2110433 | FL summary #3 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| R1-2110554 | FL summary #4 on duplex operation for RedCap | Moderator (Qualcomm Inc.) |
| R1-2110610 | FL summary #5 on duplex operation for RedCap | Moderator (Qualcomm) |
| 8.6.1.3 | Other aspects | |
| R1-2108822 | Other UE complexity reduction aspects for RedCap | Ericsson |
| R1-2109232 | Discussion on other aspects related to complexity reduction | CATT |
| R1-2109289 | Discussion on potential modification of existing DCI formats | CMCC |
| R1-2109334 | Discussion on other issues for RedCap | ZTE, Sanechips |
| R1-2109419 | Discussion on the DCI format for RedCap | Xiaomi |
| R1-2109432 | Other UE Complexity Reduction Aspects | Nokia, Nokia Shanghai Bell |
| R1-2109498 | Other aspects for complexity reduction for RedCap UEs | Samsung |
| R1-2109619 | Other aspects on UE complexity reduction for RedCap | Intel Corporation |
| R1-2109728 | Discussion on L2 buffer size reduction | Sierra Wireless. S.A. |
| R1-2109751 | Other complexity reduction aspects for RedCap UEs | Huawei, HiSilicon |
| R1-2109760 | Discussion on UE Capability of DL MIMO and Rx branches for RedCap | NEC |
| R1-2109837 | Discussion on L2 buffer size reduction for RedCap | Spreadtrum Communications, CAICT, CATT, CEPRI, China Unicom |
| R1-2109853 | Other aspects on UE complexity reduction for RedCap | Panasonic Corporation |
| R1-2109977 | Other aspects related to UE complexity reduction of RedCap | LG Electronics |
| R1-2110042 | Discussion on L2 buffer size reduction for Redcap | Apple |
| R1-2110195 | Other Aspects of UE Complexity Reduction | Qualcomm Incorporated |
| R1-2110280 | On other aspects related to RedCap UE | Nordic Semiconductor ASA |
| R1-2110444 | FL summary #1 on other aspects of UE complexity reduction for RedCap | Moderator (Intel) |
| R1-2110501 | FL summary #2 on other aspects of UE complexity reduction for RedCap | Moderator (Intel) |
| R1-2110535 | FL summary #3 on other aspects of UE complexity reduction for RedCap | Moderator (Intel) |
| R1-2110574 | FL summary #4 on other aspects of UE complexity reduction for RedCap | Moderator (Intel) |
| R1-2110591 | FL summary #5 on other aspects of UE complexity reduction for RedCap | Moderator (Intel) |
| R1-2110638 | Reply LS on L2 buffer size reduction | RAN1, Intel |
| R1-2110639 | FL summary #6 on other aspects of UE complexity reduction for RedCap | Moderator (Intel) |
| 8.6.2 | RAN1 aspects for RAN2-led features for RedCap | |
| R1-2108755 | RAN1 aspects of RedCap UE type and identification | Huawei, HiSilicon |
| R1-2108803 | Discussion on the Capabilities of RedCap UEs | FUTUREWEI |
| R1-2108823 | RAN1 aspects for RAN2-led features for RedCap | Ericsson |
| R1-2108915 | Discussion on early indication for Redcap UE | Spreadtrum Communications |
| R1-2108983 | Higher layer support for RedCap | vivo, Guangdong Genius |
| R1-2109084 | Mechanism in higher&PHY layer for Reduced Capability NR Devices | OPPO |
| R1-2109179 | RAN1 aspects for RAN2-led features for RedCap | China Unicom |
| R1-2109233 | Discussion on higher layer support of RedCap | CATT |
| R1-2109254 | Discussion on RAN1 aspects for RAN2-led features for RedCap | China Telecom |
| R1-2109290 | Discussion on RAN1 aspects for RAN2-led features for RedCap | CMCC |
| R1-2109312 | Higher layer support of Reduced Capability NR Devices | Nokia, Nokia Shanghai Bell |
| R1-2109327 | RAN1 aspects for RAN2-led features for RedCap | Lenovo, Motorola Mobility |
| R1-2109335 | Higher layer support of Reduced Capability NR devices | ZTE, Sanechips |
| R1-2109420 | Discussion on the remaining issues of higher layer related topics for RedCap | Xiaomi |
| R1-2109499 | RAN1 aspects for RAN2-led features for RedCap | Samsung |
| R1-2109620 | On RAN1 aspects for RAN2-led objectives for RedCap | Intel Corporation |
| R1-2109687 | Discussion on RAN1 aspects for RAN2-led features for RedCap | NTT DOCOMO, INC. |
| R1-2109688 | FL summary #1 on RAN1 aspects for RAN2-led features for RedCap | Moderator (Apple) |
| R1-2109726 | Design consideration for Higher layer support of RedCap | Sierra Wireless. S.A. |
| R1-2109740 | [Draft] Reply LS on capability related RAN2 agreements for RedCap | MediaTek Inc. |
| R1-2109761 | Discussion on RedCap Type definition | NEC |
| R1-2109854 | RAN1 aspects for RAN2-led features for RedCap | Panasonic Corporation |
| R1-2109950 | Remaining RAN1 aspects of RAN2-led RedCap features | InterDigital, Inc. |
| R1-2109978 | RAN1 aspects for RAN2-led features for RedCap | LG Electronics |
| R1-2109998 | RAN1 aspects for RAN2-led features for RedCap | Sharp |
| R1-2110196 | Cross-Layer Design Considerations for RedCap Device | Qualcomm Incorporated |
| R1-2110282 | On RAN1 aspects of RAN2-led RedCap features | Nordic Semiconductor ASA |
| R1-2110326 | Discussion on higher layer support of Redcap UE | WILUS Inc. |
| R1-2110451 | FL summary #2 on RAN1 aspects for RAN2-led features for RedCap | Moderator (Apple) |
| 8.6.3 | Other | |
| R1-2108824 | UE cost reduction estimates for RedCap | Ericsson |
| R1-2108984 | Discussion on L1 reduced capability signaling | vivo, Guangdong Genius |
| R1-2109234 | Views on remaining issues of RedCap | CATT |
| R1-2109291 | Discussion other aspects of RedCap UE | CMCC |
| R1-2109313 | Discussion on RedCap UE capabilities | Nokia, Nokia Shanghai Bell |
| R1-2109328 | 2-step RACH for RedCap | Lenovo, Motorola Mobility |
| R1-2109336 | Consideration on PRACH resource configuration for RedCap and CovEnh | ZTE, Sanechips |
| R1-2109421 | Discussion on the transmission of system information for RedCap | Xiaomi |
| R1-2109752 | On RedCap UE RF retuning | Huawei, HiSilicon |
| R1-2109951 | Considerations for RedCap initial BWP | InterDigital, Inc. |
| R1-2109979 | Discussion on other aspects of RedCap | LG Electronics |
| 8.7 | UE Power Saving Enhancements | |
| R1-2110616 | Session notes for 8.7 (UE Power Saving Enhancements) | Ad-hoc Chair (CMCC) |
| R1-2110679 | Summary of email discussion on Rel-17 RRC parameters for UE power saving | Moderator (MediaTek) |
| R1-2110695 | Collection of RAN1-related agreements for UE power saving enhancements for NR | Rapporteur (MediaTek) |
| 8.7.1.1 | Potential paging enhancements | |
| R1-2108744 | Paging enhancements for UE power saving in IDLE/inactive mode | Huawei, HiSilicon |
| R1-2108836 | Paging enhancements for idle/inactive UE power saving | TCL Communication Ltd. |
| R1-2108864 | Discussion on power saving enhancements for paging | ZTE, Sanechips |
| R1-2108888 | Discussion on PEI Design | Transsion Holdings |
| R1-2108916 | Discussion on potential paging enhancements for UE power saving | Spreadtrum Communications |
| R1-2108985 | Paging enhancements for idle/inactive mode UE power saving | vivo |
| R1-2109085 | Further discussion on Paging enhancements for power saving | OPPO |
| R1-2109235 | Paging enhancement for UE power saving | CATT |
| R1-2109292 | Discussion on paging early indication design | CMCC |
| R1-2109422 | Paging enhancement for power saving | Xiaomi |
| R1-2109500 | Discussion on paging enhancements | Samsung |
| R1-2109581 | On PDCCH-based PEI for paging enhancements | MediaTek Inc. |
| R1-2109582 | Summary #1 of paging enhancements | MediaTek Inc. |
| R1-2109621 | On remaining details of paging early indication design | Intel Corporation |
| R1-2109689 | Discussion on paging enhancement | NTT DOCOMO, INC. |
| R1-2109797 | Paging enhancements for idle/inactive UE power saving | Sony |
| R1-2109855 | On paging enhancement | Panasonic |
| R1-2109944 | Paging enhancement for UE power saving | Lenovo, Motorola Mobility |
| R1-2109952 | Discussion on paging enhancements for UE power saving | InterDigital, Inc. |
| R1-2109980 | Discussion on potential paging enhancements | LG Electronics |
| R1-2110043 | Paging enhancements for idle/inactive-mode UE | Apple |
| R1-2110136 | Design of Paging Enhancements | Ericsson |
| R1-2110197 | Paging enhancements for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2110283 | On paging early indication | Nordic Semiconductor ASA |
| R1-2110311 | On paging enhancements for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2110315 | Design of PDCCH-based Paging Early Indication | DENSO CORPORATION |
| R1-2110400 | Discussion on paging enhancement | NTT DOCOMO, INC. |
| R1-2110504 | Summary#2 of paging enhancements | Moderator (MediaTek) |
| R1-2110539 | Summary#3 of paging enhancements | Moderator (MediaTek) |
| R1-2110606 | Summary#4 of paging enhancements | Moderator (MediaTek) |
| R1-2110607 | [Draft] Reply LS on UE Power Saving | Moderator (MediaTek) |
| R1-2110608 | Reply LS on UE Power Saving | RAN1, MediaTek |
| R1-2110671 | Summary#5 of paging enhancements | Moderator (MediaTek) |
| 8.7.1.2 | TRS/CSI-RS occasion(s) for idle/inactive UEs | |
| R1-2108745 | Assistance RS occasions for IDLE/inactive mode | Huawei, HiSilicon |
| R1-2108837 | TRS/CSI-RS occasions for IDLE/inactive mode | TCL Communication Ltd. |
| R1-2108865 | TRS for RRC idle and inactive UEs | ZTE, Sanechips |
| R1-2108917 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Spreadtrum Communications |
| R1-2108986 | TRS/CSI-RS occasion(s) for idle/inactive UEs | vivo |
| R1-2109086 | Further discussion on RS occasion for idle/inactive UEs | OPPO |
| R1-2109236 | Configuration of TRS/CSI-RS for paging enhancement | CATT |
| R1-2109293 | Discussion on TRS/CSI-RS occasion(s) for IDLE/INACTIVE-mode UEs | CMCC |
| R1-2109423 | On TRS/CSI-RS configuration and indication for idle/inactive UEs | Xiaomi |
| R1-2109501 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Samsung |
| R1-2109502 | Moderator Summary#1 for TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2109583 | On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving | MediaTek Inc. |
| R1-2109622 | Discussion on periodic TRS occasions in idle/inactive mode | Intel Corporation |
| R1-2109690 | Discussion on TRS/CSI-RS occasion for idle/inactive Ues | NTT DOCOMO, INC. |
| R1-2109798 | On TRS/CSI-RS occasion(s) for idle/inactive UEs | Sony |
| R1-2109856 | Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive UEs | Panasonic |
| R1-2109945 | Provision of TRS/CSI-RS for idle/inactive UEs | Lenovo, Motorola Mobility |
| R1-2109953 | Remaining issues on TRS/CSI-RS occasion(s) for idle/inactive UEs | InterDigital, Inc. |
| R1-2109981 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | LG Electronics |
| R1-2109999 | Discussion on TRS/CSI-RS occasions for idle/inactive UEs | Sharp |
| R1-2110044 | Indication of TRS configurations for idle/inactive-mode UE power saving | Apple |
| R1-2110137 | Provisioning TRS occasions to Idle/Inactive UEs | Ericsson |
| R1-2110198 | TRS/CSI-RS for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2110284 | On TRS design for idle/inactive UEs | Nordic Semiconductor ASA |
| R1-2110312 | On RS information to IDLE/Inactive mode Ues | Nokia, Nokia Shanghai Bell |
| R1-2110483 | Moderator Summary #2 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2110484 | Moderator Summary #3 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2110580 | Moderator Summary #4 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2110581 | Final Moderator Summary on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| 8.7.1.3 | Other | |
| R1-2108866 | Additional simulation results of UE power consumption in RRC idle and inactive state | ZTE, Sanechips |
| R1-2108987 | Discussion on paging grouping | vivo |
| R1-2109237 | Multiple POs associated with one PEI | CATT |
| R1-2109747 | Analysis on power consumption for IDLE mode UE | Huawei, HiSilicon |
| R1-2109954 | Wake-up signal for low power wake-up radio | InterDigital, Inc. |
| R1-2110138 | Modeling of NR gNB power consumption | Ericsson |
| R1-2110199 | Aligning Paging Occasions to SSB for UE idle and inactive mode power saving | Qualcomm Incorporated |
| 8.7.2 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | |
| R1-2108746 | Extensions to Rel-16 DCI-based power saving adaptation for an active BWP | Huawei, HiSilicon |
| R1-2108867 | Extension to Rel-16 DCI-based power saving adaptation during DRX Active Time | ZTE, Sanechips |
| R1-2108918 | Discussion on power saving techniques for connected-mode UEs | Spreadtrum Communications |
| R1-2108988 | Discussion on DCI-based power saving adaptation in connected mode | vivo |
| R1-2109087 | DCI-based power saving adaptation solutions | OPPO |
| R1-2109238 | PDCCH monitoring adaptation | CATT |
| R1-2109294 | Discussion on PDCCH monitoring reduction during DRX active time | CMCC |
| R1-2109361 | Discussion on DCI-based power saving adaptation | NEC |
| R1-2109503 | Discussion on DCI-based power saving techniques | Samsung |
| R1-2109584 | On enhancements to DCI-based UE power saving during DRX active time | MediaTek Inc. |
| R1-2109623 | On remaining issues of PDCCH monitoring adaptation in active time | Intel Corporation |
| R1-2109691 | Discussion on extension to DCI-based power saving adaptation | NTT DOCOMO, INC. |
| R1-2109813 | DCI-based power saving adaptation during DRX active time | ETRI |
| R1-2109831 | Discussion on extension(s) to Rel-16 DCI-based power saving adaptation | FGI, Asia Pacific Telecom |
| R1-2109857 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | Panasonic |
| R1-2109946 | Enhanced DCI based power saving adaptation | Lenovo, Motorola Mobility |
| R1-2109955 | DCI-based power saving adaptation during DRX ActiveTime | InterDigital, Inc. |
| R1-2109982 | Discussion on DCI-based power saving adaptation during DRX ActiveTime | LG Electronics |
| R1-2110045 | Enhanced DCI-based power saving adaptation | Apple |
| R1-2110130 | A common framework for SSSG switching and PDCCH skipping | ASUSTeK |
| R1-2110139 | Design of active time power savings mechanisms | Ericsson |
| R1-2110200 | DCI-based power saving adaptation during DRX ActiveTime | Qualcomm Incorporated |
| R1-2110285 | On PDCCH monitoring adaptation | Nordic Semiconductor ASA |
| R1-2110310 | DCI-based Power Saving Enhancements | Fraunhofer HHI, Fraunhofer IIS |
| R1-2110313 | UE power saving enhancements for Active Time | Nokia, Nokia Shanghai Bell |
| R1-2110406 | FL summary#1 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2110407 | FL summary#2 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2110517 | FL summary#3 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2110518 | FL summary#4 of DCI-based power saving adaptation | Moderator (vivo) |
| 8.7.3 | Other | |
| R1-2108868 | Further discussion on potential power saving schemes for RRC connected UEs | ZTE, Sanechips |
| R1-2109239 | PDCCH skipping and SS group switching | CATT |
| R1-2109748 | Other considerations on power saving in Rel-17 | Huawei, HiSilicon |
| R1-2110140 | Evaluation results for UE power saving schemes | Ericsson |
| 8.8 | NR coverage enhancement | |
| R1-2110567 | [106bis-e-R17-RRC-CovEnh] Email discussion on Rel-17 RRC parameters for Coverage Enhancement | Moderator (China Telecom, Sharp, Nokia, Qualcomm, ZTE) |
| R1-2110617 | Session notes for 8.8 (NR coverage enhancement) | Ad-hoc Chair (CMCC) |
| R1-2110642 | Reply LS on PUCCH and PUSCH repetition | RAN1, Qualcomm |
| R1-2110688 | RAN1 agreements for Rel-17 NR coverage enhancements | WI rapporteur (China Telecom) |
| R1-2110699 | FL summary of discussion on incoming LS R1-2108703 on PUCCH and PUSCH repetitions | Moderator (Qualcomm) |
| 8.8.1.1 | Enhancements on PUSCH repetition type A | |
| R1-2108738 | Discussion on coverage enhancements for PUSCH repetition type A | Huawei, HiSilicon |
| R1-2108845 | Discussion on enhanced PUSCH repetition type A | ZTE |
| R1-2108919 | Discussion on enhancements for PUSCH repetition Type A | Spreadtrum Communications |
| R1-2108989 | Discussion on enhancement for PUSCH repetition type A | vivo |
| R1-2109088 | Enhancements on PUSCH repetition type A | OPPO |
| R1-2109240 | Discussion on enhancements on PUSCH repetition type A | CATT |
| R1-2109247 | Remaining issues on PUSCH repetition type A enhancements | China Telecom |
| R1-2109295 | Discussion on enhancements on PUSCH repetition type A | CMCC |
| R1-2109424 | Enhancements on PUSCH repetition type A | Xiaomi |
| R1-2109452 | Discussion on enhancements on PUSCH repetition type A | Rakuten Mobile, Inc |
| R1-2109455 | Discussion on enhancements on PUSCH repetition Type A | Panasonic Corporation |
| R1-2109504 | Enhancements on PUSCH repetition type A | Samsung |
| R1-2109624 | Enhancements on PUSCH repetition type A | Intel Corporation |
| R1-2109692 | Enhancements on PUSCH repetition type A | NTT DOCOMO, INC. |
| R1-2109886 | Enhancements on PUSCH repetition type A | Nokia, Nokia Shanghai Bell |
| R1-2109990 | Design considerations for PUSCH repetition Type A Enhancements | Sierra Wireless. S.A. |
| R1-2110000 | Enhancements on PUSCH repetition type A | Sharp |
| R1-2110046 | Discussion on PUSCH repetition type A enhancement | Apple |
| R1-2110096 | Discussions on PUSCH repetition type A enhancements | LG Electronics |
| R1-2110122 | PUSCH Repetition Type A Enhancement | Ericsson |
| R1-2110152 | Type-A PUSCH repetition for coverage enhancement | InterDigital, Inc. |
| R1-2110201 | Enhancements on PUSCH Repetition Type A | Qualcomm Incorporated |
| R1-2110237 | Enhancements on PUSCH repetition type A | Lenovo, Motorola Mobility |
| R1-2110327 | Discussion on enhancements on PUSCH repetition type A | WILUS Inc. |
| R1-2110448 | FL Summary #1 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2110449 | FL Summary #2 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2110450 | FL Summary #3 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2110596 | FL Summary #4 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| 8.8.1.2 | TB processing over multi-slot PUSCH | |
| R1-2108739 | Discussion on TB processing over multi-slot PUSCH | Huawei, HiSilicon |
| R1-2108846 | Discussion on TB processing over multi-slot PUSCH | ZTE |
| R1-2108920 | Discussion on TB processing over multi-slot PUSCH | Spreadtrum Communications |
| R1-2108990 | Discussion on PUSCH TB processing over multiple slots | vivo |
| R1-2109035 | Views on TB processing over multi-slot PUSCH | Fujitsu |
| R1-2109089 | Further considerations for TB over multi-slot PUSCH | OPPO |
| R1-2109133 | Discussion on TB processing over multi-slot PUSCH | NEC |
| R1-2109141 | On TB processing over multiple slots for PUSCH | Indian Institute of Tech (H) |
| R1-2109241 | Discussion on TB processing over multi-slot PUSCH | CATT |
| R1-2109248 | Remaining issues on TB processing over multi-slot PUSCH | China Telecom |
| R1-2109296 | Discussion on TB processing over multi-slot PUSCH | CMCC |
| R1-2109329 | Discussion on TBoMS PUSCH | TCL Communication Ltd. |
| R1-2109425 | Discussion on TB processing over multi-slot PUSCH | Xiaomi |
| R1-2109456 | Discussion on TB processing over multi-slot PUSCH | Panasonic Corporation |
| R1-2109505 | TB processing over multi-slot PUSCH | Samsung |
| R1-2109571 | Discussion on TB processing over multi-slot | MediaTek Inc. |
| R1-2109625 | Discussion on TB processing over multi-slot PUSCH | Intel Corporation |
| R1-2109693 | TB processing over multi-slot PUSCH | NTT DOCOMO, INC. |
| R1-2109887 | Transport block processing for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2110001 | Transport block processing over multi-slot PUSCH | Sharp |
| R1-2110047 | Discussion on TB processing over multi-slot PUSCH | Apple |
| R1-2110097 | Discussions on TB processing over multi-slot PUSCH | LG Electronics |
| R1-2110123 | TB Processing over Multi-Slot PUSCH | Ericsson |
| R1-2110153 | TB processing over multiple slots | InterDigital, Inc. |
| R1-2110202 | TB processing over multi-slot PUSCH | Qualcomm Incorporated |
| R1-2110238 | Enhancements for TB processing over multi-slot PUSCH | Lenovo, Motorola Mobility |
| R1-2110328 | Discussion on TB processing over multi-slot PUSCH | WILUS Inc. |
| R1-2110428 | FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2110528 | FL summary #2 of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2110529 | FL summary #3 of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2110530 | Final FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| 8.8.1.3 | Joint channel estimation for PUSCH | |
| R1-2108740 | Discussion on joint channel estimation for PUSCH | Huawei, HiSilicon |
| R1-2108847 | Discussion on joint channel estimation for PUSCH | ZTE |
| R1-2108921 | Discussion on joint channel estimation for PUSCH | Spreadtrum Communications |
| R1-2108991 | Discussion on joint channel estimation for PUSCH | vivo |
| R1-2109090 | Consideration on Joint channel estimation for PUSCH | OPPO |
| R1-2109242 | Discussion on joint channel estimation for PUSCH | CATT |
| R1-2109249 | Remaining issues on joint channel estimation for PUSCH | China Telecom |
| R1-2109250 | FL Summary of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2109297 | Discussion on joint channel estimation for PUSCH | CMCC |
| R1-2109330 | Discussion on joint channel estimation for PUSCH | TCL Communication Ltd. |
| R1-2109426 | Discussion on joint channel estimation for PUSCH | Xiaomi |
| R1-2109459 | Discussion on joint channel estimation for PUSCH | Panasonic Corporation |
| R1-2109506 | Joint channel estimation for PUSCH | Samsung |
| R1-2109572 | Discussion on Joint channel estimation over multi-slot | MediaTek Inc. |
| R1-2109626 | Discussion on joint channel estimation for PUSCH | Intel Corporation |
| R1-2109694 | Joint channel estimation for PUSCH | NTT DOCOMO, INC. |
| R1-2109799 | Views on Joint Channel Estimation for PUSCH | Sony |
| R1-2109888 | Joint channel estimation for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2109991 | Design Considerations for Joint channel estimation for PUSCH | Sierra Wireless. S.A. |
| R1-2110002 | Joint channel estimation for multiple PUSCH transmission | Sharp |
| R1-2110048 | Discussion on joint channel estimation for PUSCH | Apple |
| R1-2110098 | Discussions on joint channel estimation for PUSCH | LG Electronics |
| R1-2110124 | Joint Channel Estimation for PUSCH | Ericsson |
| R1-2110154 | Joint channel estimation for PUSCH | InterDigital, Inc. |
| R1-2110203 | Joint channel estimation for PUSCH | Qualcomm Incorporated |
| R1-2110239 | Enhancements for joint channel estimation for multiple PUSCH | Lenovo, Motorola Mobility |
| R1-2110329 | Discussion on joint channel estimation for PUSCH | WILUS Inc. |
| R1-2110502 | FL Summary#2 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2110503 | FL Summary#3 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2110568 | FL Summary#4 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2110569 | [106bis-e-NR-R17-CovEnh-03] Summary of email discussion on joint channel estimation for PUSCH | Moderator (China Telecom) |
| 8.8.2 | PUCCH enhancements | |
| R1-2108741 | Discussion on PUCCH coverage enhancement | Huawei, HiSilicon |
| R1-2108848 | Discussion on coverage enhancements for PUCCH | ZTE |
| R1-2108922 | Discussion on PUCCH enhancements | Spreadtrum Communications |
| R1-2108992 | Discussion on PUCCH enhancements | vivo |
| R1-2109091 | PUCCH enhancements for coverage | OPPO |
| R1-2109243 | Discussion on PUCCH enhancement | CATT |
| R1-2109251 | Remaining issues on PUCCH enhancements | China Telecom |
| R1-2109298 | Discussion on PUCCH enhancements | CMCC |
| R1-2109427 | Discussion on PUCCH enhancements | Xiaomi |
| R1-2109457 | Discussion on PUCCH enhancement for NR coverage enhancement | Panasonic Corporation |
| R1-2109507 | PUCCH enhancements | Samsung |
| R1-2109627 | Discussion on PUCCH enhancements | Intel Corporation |
| R1-2109695 | PUCCH enhancements for coverage enhancement | NTT DOCOMO, INC. |
| R1-2109814 | PUCCH enhancements | ETRI |
| R1-2109889 | PUCCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2110003 | PUCCH coverage enhancement | Sharp |
| R1-2110049 | PUCCH coverage enhancement | Apple |
| R1-2110099 | Discussions on coverage enhancement for PUCCH | LG Electronics |
| R1-2110125 | PUCCH Dynamic Repetition and DMRS Bundling | Ericsson |
| R1-2110155 | Discussions on PUCCH enhancements | InterDigital, Inc. |
| R1-2110204 | PUCCH enhancements | Qualcomm Incorporated |
| R1-2110240 | Enhancements for PUCCH repetition | Lenovo, Motorola Mobility |
| R1-2110441 | FL summary#1 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2110513 | FL summary#2 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2110590 | FL summary #3 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| 8.8.3 | Type A PUSCH repetitions for Msg3 | |
| R1-2108742 | Discussion on Msg3 repetition for coverage enhancement | Huawei, HiSilicon |
| R1-2108849 | Discussion on support of Type A PUSCH repetitions for Msg3 | ZTE |
| R1-2108923 | Discussion on Type A PUSCH repetitions for Msg3 | Spreadtrum Communications |
| R1-2108993 | Discussion on Type A PUSCH repetitions for Msg3 | vivo |
| R1-2109092 | Type A PUSCH repetitions for Msg3 coverage | OPPO |
| R1-2109134 | Discussion on PUSCH repetition for Msg3 | NEC |
| R1-2109244 | Discussion on Type A PUSCH repetitions for Msg3 | CATT |
| R1-2109252 | Remaining issues on type A PUSCH repetitions for Msg3 | China Telecom |
| R1-2109299 | Discussion on type A PUSCH repetitions for Msg3 | CMCC |
| R1-2109428 | Discussion on Type A PUSCH repetition for Msg3 | Xiaomi |
| R1-2109458 | Discussion on Type A PUSCH repetitions for Msg.3 | Panasonic Corporation |
| R1-2109508 | Type A PUSCH repetitions for Msg3 | Samsung |
| R1-2109628 | On Msg3 PUSCH repetition | Intel Corporation |
| R1-2109696 | Type A PUSCH repetitions for Msg3 | NTT DOCOMO, INC. |
| R1-2109815 | Type A PUSCH repetitions for Msg3 | ETRI |
| R1-2109890 | Approaches and solutions for Type A PUSCH repetitions for Msg3 | Nokia, Nokia Shanghai Bell |
| R1-2110004 | Type-A PUSCH repetition for msg3 | Sharp |
| R1-2110050 | Discussion on Msg3 Coverage Enhancement | Apple |
| R1-2110100 | Discussion on coverage enhancement for Msg3 PUSCH | LG Electronics |
| R1-2110126 | Type A PUSCH Repetition for Msg3 | Ericsson |
| R1-2110205 | Type A PUSCH repetition for Msg3 | Qualcomm Incorporated |
| R1-2110236 | Type A PUSCH repetitions for Msg3 | InterDigital, Inc. |
| R1-2110330 | Discussion on Type A PUSCH repetitions for Msg3 | WILUS Inc. |
| R1-2110417 | Feature lead summary #1 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2110418 | Feature lead summary #2 on support of Type A PUSCH repetitions for Msg4 | Moderator (ZTE) |
| R1-2110419 | Feature lead summary #3 on support of Type A PUSCH repetitions for Msg5 | Moderator (ZTE) |
| R1-2110585 | Reply LS on Msg3 repetition in coverage enhancement | RAN1, ZTE |
| R1-2110589 | Summary of discussion on reply LS for Msg3 repetition in coverage enhancement | Moderator (ZTE) |
| 8.8.4 | Other | |
| R1-2108850 | Performance impacts of residual frequency error for joint channel estimation of PUSCH and PUCCH transmissions | ZTE |
| R1-2108994 | Enhanced contention resolution mechanism for CBRA procedure with MSG3 PUSCH repetition | vivo |
| R1-2109245 | Views on reusing PUSCH enhancements for Msg3 | CATT |
| R1-2109429 | Other considerations for coverage enhancement | Xiaomi |
| R1-2109509 | Considerations on Rel-17 RRC parameters for Coverage Enhancement | Samsung |
| R1-2109746 | On further potential coverage enhancements | Huawei, HiSilicon |
| R1-2109891 | On the support of DMRS bundling for the scenario of other UL transmission in-between PUSCH/PUCCH repetitions | Nokia, Nokia Shanghai Bell |
| R1-2110127 | Frequency Hopping for TBoMS | Ericsson |
| 8.9 | Rel-17 enhancements for NB-IoT and LTE-MTC | |
| R1-2110618 | Session notes for 8.9 (Rel-17 enhancements for NB-IoT and LTE-MTC) | Ad-hoc Chair (CMCC) |
| R1-2110650 | Feature lead summary on 106bis-e-R17-RRC-NB-IoT-eMTC | Moderator (Huawei) |
| R1-2110691 | RAN1 agreements of Additional enhancements for NB-IoT and LTE-MTC | WI rapporteur (Huawei) |
| 8.9.1 | Support of 16-QAM for unicast in UL and DL for NB-IoT | |
| R1-2108777 | Support of 16QAM for unicast in UL and DL in NB-IoT | Huawei, HiSilicon |
| R1-2109174 | Support of 16-QAM for NB-IoT | Qualcomm Incorporated |
| R1-2109314 | Support of 16-QAM for NB-IoT | Nokia, Nokia Shanghai Bell |
| R1-2109320 | Support 16QAM for NBIoT | Lenovo, Motorola Mobility |
| R1-2109337 | Discussion on UL and DL 16QAM for NB-IoT | ZTE, Sanechips |
| R1-2109559 | Remaining Issues on supporting 16QAM in NB-IOT R17 | MediaTek Inc. |
| R1-2110316 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| R1-2110459 | Feature lead summary #1 on 106bis-e-LTE-Rel17-NB-IoT-eMTC-01 | Moderator (Huawei) |
| R1-2110555 | Feature lead summary #2 on 106bis-e-LTE-Rel17-NB-IoT-eMTC-01 | Moderator (Huawei) |
| 8.9.2 | Support additional PDSCH scheduling delay for introduction of 14-HARQ processes in DL for eMTC | |
| R1-2108778 | Support of 14-HARQ processes in DL for HD-FDD MTC UEs | Huawei, HiSilicon |
| R1-2109175 | Support of 14 HARQ processes and scheduling delay | Qualcomm Incorporated |
| R1-2109315 | Support of 14-HARQ processes in DL for eMTC | Nokia, Nokia Shanghai Bell |
| R1-2109338 | Remaining issues on 14-HARQ processes in DL for eMTC | ZTE, Sanechips |
| R1-2110317 | Support of 14 HARQ processes in DL in LTE-MTC | Ericsson |
| R1-2110413 | Feature Lead Summary [106bis-e-LTE-Rel17-NB-IoT-eMTC-02] - first checkpoint | Moderator (Ericsson) |
| R1-2110414 | Feature Lead Summary [106bis-e-LTE-Rel17-NB-IoT-eMTC-02] - final checkpoint | Moderator (Ericsson) |
| 8.9.3 | Other | |
| R1-2110318 | On the support of 16-QAM for unicast in UL and DL for TDD NB-IoT | Ericsson |
| R1-2110372 | Discussion on RRC parameters for max DL TBS of 1736 bits | Huawei, HiSilicon |
| 8.10 | Enhancements to Integrated Access and Backhaul | |
| R1-2110692 | RAN1 decisions for Rel-17 eIAB | WI rapporteur (Qualcomm) |
| R1-2110701 | Summary of [106bis-e-R17-RRC-eIAB] Email discussion on Rel-17 RRC parameters for eIAB | Moderator (Qualcomm) |
| 8.10.1 | Enhancements to resource multiplexing between child and parent links of an IAB node | |
| R1-2108765 | Resource multiplexing between backhaul and access for IAB duplexing enhancements | Huawei, HiSilicon |
| R1-2108826 | Enhancements for resource multiplexing among IAB backhaul and access links | Nokia, Nokia Shanghai Bell |
| R1-2108995 | Enhancement to resource multiplexing between child and parent links | vivo |
| R1-2109261 | Enhancements to the IAB resource multiplexing | ZTE, Sanechips |
| R1-2109510 | Enhancements to Resource Multiplexing for NR IAB | Samsung |
| R1-2109629 | Enhancements to Resource Multiplexing between Child and Parent Links of an IAB Node | Intel Corporation |
| R1-2109697 | Resource multiplexing between child and parent links of an IAB node | NTT DOCOMO, INC. |
| R1-2109816 | Discussion on IAB resource multiplexing enhancements | ETRI |
| R1-2109839 | Discussions on enhancements to resource multiplexing between child and parent links of an IAB node | CEWiT |
| R1-2109920 | Enhancements for IAB resource multiplexing | AT&T |
| R1-2109936 | Resource multiplexing in enhanced IAB systems | Lenovo, Motorola Mobility |
| R1-2110051 | Enhanced resource multiplexing within and across IAB nodes | Apple |
| R1-2110101 | Discussions on IAB resource multiplexing enhancements | LG Electronics |
| R1-2110206 | Resource management for enhanced duplexing | Qualcomm Incorporated |
| R1-2110331 | Resource multiplexing and dual connectivity in enhanced IAB | Ericsson |
| R1-2110442 | Feature lead summary #1 of 8.10.1 | Moderator (AT&T) |
| R1-2110443 | Feature lead summary #2 of 8.10.1 | Moderator (AT&T) |
| 8.10.2 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | |
| R1-2108766 | Enhancements for simultaneous operation of MT and DU | Huawei, HiSilicon |
| R1-2108827 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | Nokia, Nokia Shanghai Bell |
| R1-2108996 | Other enhancements for simultaneous operation of child and parent links | vivo |
| R1-2109262 | Enhancements for simultaneous operation of child and parent links | ZTE, Sanechips |
| R1-2109511 | Enhancements to Timing, Power Control and CLI for NR IAB | Samsung |
| R1-2109630 | Other Enhancements for Simultaneous Operations | Intel Corporation |
| R1-2109698 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | NTT DOCOMO, INC. |
| R1-2109817 | Discussion on simultaneous operation enhancements for eIAB | ETRI |
| R1-2109840 | Discussion on simultaneous operation of IAB-node’s child and parent links | CEWiT |
| R1-2109921 | Enhancements for IAB interference management | AT&T |
| R1-2109937 | Timing, interference, and power control in enhanced IAB systems | Lenovo, Motorola Mobility |
| R1-2110052 | Other enhancements for simultaneous operation of an IAB node's links | Apple |
| R1-2110102 | Discussions on other enhancement for simultaneous operation | LG Electronics |
| R1-2110207 | Enhancements for simultaneous operation of IAB-node's child and parent links | Qualcomm Incorporated |
| R1-2110332 | Timing, interference management and power control in enhanced IAB | Ericsson |
| R1-2110497 | Summary#1 [106bis-e-NR-eIAB-02] on other enhancements for simultaneous operation of IAB-node’s child and parent links | Moderator (Qualcomm) |
| R1-2110515 | Final summary [106bis-e-NR-eIAB-02] on other enhancements for simultaneous operation of IAB-node’s child and parent links | Moderator (Qualcomm) |
| 8.10.3 | Other | |
| R1-2108828 | Discussion on inter-donor IAB migration and topology redundancy | Nokia, Nokia Shanghai Bell |
| R1-2108997 | Other enhancements to Rel-17 IAB nodes | vivo |
| R1-2109263 | Consideration on reference carrier for semi-static IAB-DU resource configuration | ZTE, Sanechips |
| R1-2109755 | Other enhancements for IAB | Huawei, HiSilicon |
| R1-2110333 | On RRC parameters in enhanced IAB | Ericsson |
| 8.11 | NR Sidelink enhancement | |
| R1-2110649 | [106bis-e-R17-RRC-Sidelink] Summary of email discussion on Rel-17 RRC parameters for sidelink enhancement | Moderator (LG Electronics) |
| R1-2110676 | Summary of RAN1 agreements for Rel-17 NR sidelink enhancement | WI rapporteur (LG Electronics) |
| 8.11.1 | Resource allocation enhancement | |
| R1-2110511 | Moderator summary for [106bis-e-NR-R17-Sidelink-03] Reply LS to R1-2108710 | Moderator (InterDigital) |
| R1-2110662 | Reply LS on SL resource selection with DRX | RAN1, InterDigital |
| 8.11.1.1 | Resource allocation for power saving | |
| R1-2108763 | Sidelink resource allocation to reduce power consumption | Huawei, HiSilicon |
| R1-2108800 | Power consumption reduction for sidelink resource allocation | FUTUREWEI |
| R1-2108818 | Resource allocation for power saving | Nokia, Nokia Shanghai Bell |
| R1-2108924 | Discussion on sidelink resource allocation for power saving | Spreadtrum Communications |
| R1-2108998 | Resource allocation for sidelink power saving | vivo |
| R1-2109036 | Considerations on partial sensing and DRX in NR Sidelink | Fujitsu |
| R1-2109059 | Discussion on power saving in NR sidelink communication | OPPO |
| R1-2109129 | Discussion on resource allocation for power saving | NEC |
| R1-2109191 | Further discussion on sidelink resource allocation enhancements for power saving | CATT, GOHIGH |
| R1-2109300 | Discussion on resource allocation for power saving | CMCC |
| R1-2109348 | Considerations on partial sensing mechanism of NR V2X | CAICT |
| R1-2109384 | Discussion on sidelink resource allocation enhancement for power saving | Xiaomi |
| R1-2109430 | NR Sidelink Resource Allocation for UE Power Saving | Fraunhofer HHI, Fraunhofer IIS |
| R1-2109512 | On Resource Allocation for Power Saving | Samsung |
| R1-2109541 | Sidelink resource allocation for power saving | Lenovo, Motorola Mobility |
| R1-2109564 | Remaining issues on sidelink power saving | MediaTek Inc. |
| R1-2109631 | Sidelink Resource Allocation Schemes for UE Power Saving | Intel Corporation |
| R1-2109699 | Discussion on sidelink resource allocation for power saving | NTT DOCOMO, INC. |
| R1-2109731 | Discussion on Sidelink Resource Allocation for Power Saving | Panasonic Corporation |
| R1-2109732 | Discussion on resource allocation for power saving | ZTE, Sanechips |
| R1-2109800 | Discussion on sidelink resource allocation for power saving | Sony |
| R1-2109818 | Discussion on resource allocation for power saving | ETRI |
| R1-2109860 | Discussion on resource allocation for power saving | LG Electronics |
| R1-2109883 | Sidelink resource allocation for power saving | InterDigital, Inc. |
| R1-2110005 | Discussion on resource allocation for power saving | Sharp |
| R1-2110053 | On Sidelink Resource Allocation for Power Saving | Apple |
| R1-2110116 | Discussion on NR SL Resource Allocation for Power Saving | Convida Wireless |
| R1-2110131 | Discussion on partial sensing and SL DRX impact | ASUSTeK |
| R1-2110208 | Power Savings for Sidelink | Qualcomm Incorporated |
| R1-2110305 | Resource allocation for power saving in NR sidelink enhancement | ITL |
| R1-2110307 | Further discussion on power saving for sidelink resource allocation | ROBERT BOSCH GmbH |
| R1-2110339 | Resource allocation procedures for power saving | Ericsson |
| R1-2110476 | FL summary for AI 8.11.1.1 – resource allocation for power saving (before 1st GTW) | Moderator (OPPO) |
| R1-2110477 | FL summary for AI 8.11.1.1 – resource allocation for power saving (before 2nd GTW) | Moderator (OPPO) |
| R1-2110478 | FL summary for AI 8.11.1.1 – resource allocation for power saving (before 3rd GTW) | Moderator (OPPO) |
| R1-2110479 | FL summary for AI 8.11.1.1 – resource allocation for power saving (before 4th GTW) | Moderator (OPPO) |
| R1-2110480 | FL summary for AI 8.11.1.1 – resource allocation for power saving (EOM) | Moderator (OPPO) |
| 8.11.1.2 | Inter-UE coordination for Mode 2 enhancements | |
| R1-2108764 | Inter-UE coordination in sidelink resource allocation | Huawei, HiSilicon |
| R1-2108801 | Discussion on techniques for inter-UE coordination | FUTUREWEI |
| R1-2108819 | Inter-UE coordination for Mode 2 enhancements | Nokia, Nokia Shanghai Bell |
| R1-2108925 | Discussion on inter-UE coordination in sidelink resource allocation | Spreadtrum Communications |
| R1-2108999 | Discussion on mode-2 enhancements | vivo |
| R1-2109037 | Considerations on inter-UE coordination for mode 2 enhancements | Fujitsu |
| R1-2109060 | Inter-UE coordination in mode 2 of NR sidelink | OPPO |
| R1-2109130 | Discussion on mode 2 enhancements | NEC |
| R1-2109142 | Inter-UE coordination for enhanced resource allocation | Mitsubishi Electric RCE |
| R1-2109192 | Discussion on Inter-UE coordination for Mode 2 enhancements | CATT, GOHIGH |
| R1-2109301 | Discussion on inter-UE coordination for mode 2 enhancement | CMCC |
| R1-2109341 | Feasibility and benefits for NR Sidelink mode 2 enhancements | CEWiT |
| R1-2109349 | Considerations on mode 2 enhancements | CAICT |
| R1-2109385 | Discussion on inter-UE coordination | Xiaomi |
| R1-2109431 | Resource Allocation Enhancements for Mode 2 | Fraunhofer HHI, Fraunhofer IIS |
| R1-2109449 | Discussion on inter-UE coordination for mode 2 enhancements | Zhejiang Lab |
| R1-2109450 | Discussion on inter-UE coordination for Mode 2 enhancements | Hyundai Motors |
| R1-2109513 | On Inter-UE Coordination for Mode2 Enhancements | Samsung |
| R1-2109542 | Inter-UE coordination for Mode 2 enhancements | Lenovo, Motorola Mobility |
| R1-2109586 | Discussion on Mode 2 enhancements | MediaTek Inc. |
| R1-2109632 | Solutions for sidelink communication with inter-UE coordination feedback | Intel Corporation |
| R1-2109700 | Resource allocation for reliability and latency enhancements | NTT DOCOMO, INC. |
| R1-2109758 | Inter-UE coordination for Mode 2 enhancements | Panasonic Corporation |
| R1-2109801 | Discussion on inter-UE coordination for Mode 2 enhancements | Sony |
| R1-2109819 | Discussion on inter-UE coordination for Mode 2 enhancements | ETRI |
| R1-2109852 | Discussion on inter-UE coordination | ZTE |
| R1-2109861 | Discussion on inter-UE coordination for Mode 2 enhancements | LG Electronics |
| R1-2109884 | On inter-UE coordination for Mode 2 enhancement | InterDigital, Inc. |
| R1-2110006 | Discussion on inter-UE coordination for mode 2 enhancements | Sharp |
| R1-2110054 | On Inter-UE Coordination | Apple |
| R1-2110117 | Discussion on Inter-UE Coordination for NR SL Mode 2 Enhancement | Convida Wireless |
| R1-2110132 | Discussion on V2X mode 2 enhancements | ASUSTeK |
| R1-2110209 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2110306 | Support of inter-UE coordination scheme 1 and scheme 2 | ROBERT BOSCH GmbH |
| R1-2110340 | Details on mode 2 enhancements for inter-UE coordination | Ericsson |
| R1-2110648 | Feature lead summary for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2110674 | Feature lead summary for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| 8.11.2 | Other | |
| R1-2109000 | Other aspects on SL enhancements | vivo |
| R1-2109061 | Wake up signal for NR sidelink | OPPO |
| R1-2109193 | Discussion on SL DRX configuration granularity | CATT, GOHIGH |
| R1-2109386 | Discussion on other design aspects for sidelink enhancement | Xiaomi |
| R1-2109514 | Discussion on Sidelink Enhancement | Samsung |
| R1-2109734 | BWP configuration for power saving | ZTE, Sanechips |
| R1-2109754 | Physical layer impacts of sidelink DRX | Huawei, HiSilicon |
| R1-2109885 | On gNB-designated resources for inter-UE coordination and sensing in SL DRX | InterDigital, Inc. |
| R1-2110055 | Network Assisted Resource Selection | Apple |
| R1-2110341 | Additional enhancements to resource allocation procedures | Ericsson |
| R1-2110586 | Reply LS on synchronous operation between Uu and SL in TDD band n79 | RAN1, GOHIGH |
| R1-2110593 | Summary for email discussion [106bis-e-NR-R17-Sidelink-04] | Moderator (CATT) |
| 8.12 | NR Multicast and Broadcast Services | |
| R1-2110619 | Session notes for 8.12 (NR Multicast and Broadcast Services) | Ad-Hoc Chair (Ericsson) |
| R1-2110689 | Agreements for NR MBS up to RAN1#106b | WI rapporteur (CMCC) |
| R1-2110694 | Summary of email discussion on Rel-17 RRC parameters for NR MBS | Moderator (CMCC, Huawei, BBC) |
| R1-2110696 | Agreements for NR MBS up to RAN1#106b | WI rapporteur (CMCC) |
| 8.12.1 | Mechanisms to support group scheduling for RRC_CONNECTED UEs | |
| R1-2108723 | Resource configuration and group scheduling for RRC_CONNECTED UEs | Huawei, HiSilicon, CBN |
| R1-2108804 | Group Scheduling Aspects for Connected UEs | FUTUREWEI |
| R1-2108851 | Discussion on Mechanisms to Support Group Scheduling for RRC_CONNECTED UEs | ZTE |
| R1-2108926 | Discussion on MBS group scheduling for RRC_CONNETED UEs | Spreadtrum Communications |
| R1-2109001 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED Ues | vivo |
| R1-2109067 | Discussion on group Scheduling mechanism for RRC_CONNECTED UEs | OPPO |
| R1-2109135 | Discussion on Group Scheduling Mechanisms for RRC_CONNECTED Ues | NEC |
| R1-2109194 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2109302 | Summary#1 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2109303 | Discussion on group scheduling mechanisms | CMCC |
| R1-2109316 | Group Scheduling Mechanisms to Support 5G Multicast / Broadcast Services for RRC_CONNECTED Ues | Nokia, Nokia Shanghai Bell |
| R1-2109387 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UE | Xiaomi |
| R1-2109515 | Support of group scheduling for RRC_CONNECTED UEs | Samsung |
| R1-2109538 | On group scheduling mechanism for RRC_CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2109567 | Discussion on NR MBS group scheduling for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2109633 | NR-MBS Group Scheduling for RRC_CONNECTED UEs | Intel Corporation |
| R1-2109701 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | NTT DOCOMO, INC. |
| R1-2109767 | Group scheduling related questions for RRC_CONNECTED UEs | TD Tech |
| R1-2109823 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | FGI, Asia Pacific Telecom |
| R1-2109983 | Support of group scheduling for RRC_CONNECTED UEs | LG Electronics |
| R1-2110056 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Apple |
| R1-2110074 | Discussion on common frequency resource configuration for multicast of RRC_CONNECTED UEs | ETRI |
| R1-2110118 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Convida Wireless |
| R1-2110210 | Views on group scheduling for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2110249 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Google Inc. |
| R1-2110255 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | ASUSTeK |
| R1-2110355 | Mechanisms to support MBS group scheduling for RRC_CONNECTED Ues | Ericsson |
| R1-2110465 | Summary#2 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2110466 | Summary#3 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2110467 | Summary#4 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2110543 | Summary#5 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2110544 | Summary#6 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2110637 | Final summary on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| 8.12.2 | Mechanisms to improve reliability for RRC_CONNECTED UEs | |
| R1-2108724 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Huawei, HiSilicon, CBN |
| R1-2108805 | Further Discussions on Reliability for RRC_CONNECTED UEs | FUTUREWEI |
| R1-2108852 | Discussion on Mechanisms to Improve Reliability for RRC_CONNECTED UEs | ZTE |
| R1-2108927 | Mechanisms to improve MBS reliability for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2109002 | Discussion on mechanisms to improve reliability for RRC_CONNECTED Ues | vivo |
| R1-2109068 | UL feedback for RRC-CONNECTED UEs in MBS | OPPO |
| R1-2109136 | Discussion on Reliability Improvements for RRC_CONNECTED UEs | NEC |
| R1-2109195 | Discussion on reliability improvement mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2109304 | Discussion on reliability improvement | CMCC |
| R1-2109317 | Reliability Improvements for RRC_CONNECTED UEs | Nokia, Nokia Shanghai Bell |
| R1-2109516 | On mechanisms to improve reliability for RRC_CONNECTED UEs | Samsung |
| R1-2109539 | On reliability improvement for RRC-CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2109568 | Discussion on mechanisms to improve reliability for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2109634 | Mechanisms to Improve Reliability of NR-MBS for RRC_CONNECTED UEs | Intel Corporation |
| R1-2109702 | Discussion on mechanisms to improve reliability for multicast for RRC_CONNECTED UEs | NTT DOCOMO, INC. |
| R1-2109768 | PUCCH formats for NACK-ONLY based HARQ-ACK feedback | TD Tech |
| R1-2109984 | Mechanisms to improve reliability of Broadcast/Multicast service | LG Electronics |
| R1-2110057 | Discussion on MBS reliability improvement for RRC_CONNECTED UEs | Apple |
| R1-2110075 | Discussion on HARQ-ACK feedback mechanism for multicast of RRC_CONNECTED UEs | ETRI |
| R1-2110119 | Discussion on reliability enhancement for RRC_CONNECTED UEs | Convida Wireless |
| R1-2110211 | Views on UE feedback for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2110250 | Discussion on MBS reliability for RRC_CONNECTED UEs | Google Inc. |
| R1-2110356 | Mechanisms to improve reliability for RRC_CONNECTED Ues | Ericsson |
| R1-2110408 | FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2110493 | FL summary#2 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2110526 | FL summary#3 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2110545 | FL summary#4 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2110583 | FL summary#5 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2110646 | FL summary#6 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| 8.12.3 | Basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | |
| R1-2108725 | Discussion on UE receiving broadcast in RRC IDLE/INACTIVE state | Huawei, HiSilicon, CBN |
| R1-2108806 | MBS Support for RRC IDLE/INACTIVE UEs | FUTUREWEI |
| R1-2108853 | Discussion on basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | ZTE |
| R1-2108928 | Basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | Spreadtrum Communications |
| R1-2109003 | Remaining issues on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE Ues | vivo |
| R1-2109069 | Discussion on basic functions for RRC_IDLE/RRC_INACTIVE UEs | OPPO |
| R1-2109196 | Discussion on basic functions for broadcast multicast for RRC_IDLE RRC_INACTIVE UEs | CATT |
| R1-2109305 | Discussion on NR MBS in RRC_IDLE/ RRC_INACTIVE states | CMCC |
| R1-2109318 | Basic Functions for Broadcast / Multicast for RRC_IDLE / RRC_INACTIVE Ues | Nokia, Nokia Shanghai Bell |
| R1-2109388 | Discussion on basic functions for broadcast/multicast for RRC_IDLERRC_INACTIVE UEs | Xiaomi |
| R1-2109517 | On basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Samsung |
| R1-2109540 | Basic functions for broadcast/multicast in idle/inactive states | Lenovo, Motorola Mobility |
| R1-2109569 | Discussion on MBS for RRC_IDLE/INACTIVE UEs | MediaTek Inc. |
| R1-2109635 | NR-MBS for RRC_IDLE/INACTIVE UEs | Intel Corporation |
| R1-2109703 | Discussion on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | NTT DOCOMO, INC. |
| R1-2109769 | Further discussion on basic functions for RRC_IDLE/RRC_INACTIVE UEs | TD Tech, Chengdu TD Tech |
| R1-2109802 | Considerations on MBS functions for RRC_IDLE/INACTIVE UEs | Sony |
| R1-2109985 | Basic function for broadcast/multicast | LG Electronics |
| R1-2110058 | Discussion on MBS for RRC_IDLE and RRC_INACTIVE UEs | Apple |
| R1-2110120 | Discussion on MBS for RRC_IDLE/RRC_INACTIVE UEs | Convida Wireless |
| R1-2110212 | Views on group scheduling for Broadcast RRC_IDLE/INACTIVE UEs | Qualcomm Incorporated |
| R1-2110251 | Discussion on MBS for RRC_IDLE/RRC_INACTIVE UEs | Google Inc. |
| R1-2110258 | Discussion on basic functions for broadcast or multicast for RRC_IDLE and RRC_INACTIVE UEs | ASUSTeK |
| R1-2110357 | Support for NR multicast reception in RRC Inactive/Idle | Ericsson |
| R1-2110409 | Feature Lead summary #1 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2110410 | Feature Lead summary #2 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2110411 | Feature Lead summary #3 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2110412 | Feature Lead summary #4 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2110595 | Feature Lead summary #5 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| 8.12.4 | Other | |
| R1-2108854 | Consideration on potential further enhancement for MBS | ZTE |
| R1-2109004 | Other issues for Rel-17 MBS | vivo |
| R1-2109197 | Discussion on other issues in Rel-17 MBS | CATT |
| R1-2109319 | Other Aspects for Rel-17 MBS | Nokia, Nokia Shanghai Bell |
| R1-2109389 | Discussion on remaining issues for idle and inactive UE | Xiaomi |
| R1-2109742 | Impact from MCCH and MTCH on broadcast reception | Huawei, HiSilicon |
| R1-2109770 | Discussion on typical configuration for NR MBS | CHENGDU TD TECH LTD. |
| R1-2109986 | Other aspects for MBS | LG Electronics |
| R1-2110358 | Assumptions for performance evaluations of NR-MBS | Ericsson |
| 8.13 | NR Dynamic spectrum sharing (DSS) | |
| R1-2110620 | Session notes for 8.13 (NR Dynamic spectrum sharing (DSS)) | Ad-hoc Chair (CMCC) |
| R1-2110665 | Summary of Email discussion [106bis-e-R17-RRC-DSS] | Moderator (Ericsson) |
| 8.13.1 | Cross-carrier scheduling (from Scell to Pcell) | |
| R1-2108773 | Discussion on SCell PDCCH scheduling P(S)Cell PDSCH or PUSCH | Huawei, HiSilicon |
| R1-2108855 | Discussion on Cross-Carrier Scheduling from SCell to PCell | ZTE |
| R1-2108929 | Discussion on cross-carrier scheduling from SCell to Pcell | Spreadtrum Communications |
| R1-2109005 | Discussion on Scell scheduling Pcell | vivo |
| R1-2109098 | Discussion on cross-carrier scheduling from Scell to Pcell | OPPO |
| R1-2109306 | Discussion on cross-carrier scheduling from SCell to Pcell | CMCC |
| R1-2109390 | Discussion on cross-carrier scheduling from SCell to PCell | Xiaomi |
| R1-2109518 | Cross-carrier scheduling from SCell to PCell | Samsung |
| R1-2109551 | On Cross-Carrier Scheduling from sSCell to P(S)Cell | MediaTek Inc. |
| R1-2109636 | On SCell scheduling PCell transmissions | Intel Corporation |
| R1-2109704 | Discussion on cross-carrier scheduling enhancements for NR DSS | NTT DOCOMO, INC. |
| R1-2109820 | Discussion on cross-carrier scheduling from SCell to Pcell | ETRI |
| R1-2109895 | Discussion on cross carrier scheduling from sSCell to PCell | InterDigital, Inc. |
| R1-2109938 | Cross-carrier scheduling (from Scell to Pcell) | Lenovo, Motorola Mobility |
| R1-2109987 | Discussion on cross-carrier scheduling from SCell to Pcell | LG Electronics |
| R1-2110059 | Views on Rel-17 DSS SCell scheduling PCell | Apple |
| R1-2110141 | Enhanced cross-carrier scheduling for DSS | Ericsson |
| R1-2110213 | Cross-carrier scheduling from an SCell to the PCell/PSCell | Qualcomm Incorporated |
| R1-2110294 | On cross-carrier scheduling from SCell to Pcell | Nokia, Nokia Shanghai Bell |
| R1-2110376 | On cross-carrier scheduling from SCell to Pcell | Nokia, Nokia Shanghai Bell |
| R1-2110452 | Summary of Email discussion [106bis-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2110507 | Summary#2 of Email discussion [106bis-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2110557 | Summary#3 of Email discussion [106bis-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2110664 | Summary#4 of Email discussion [106bis-e-NR-DSS-01] | Moderator (Ericsson) |
| 8.13.2 | Support efficient activation/de-activation mechanism for SCells in NR CA | |
| R1-2108774 | Discussion on efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2108797 | Support efficient activation/de-activation mechanism for Scells | FUTUREWEI |
| R1-2108856 | Discussion on Support Efficient Activation De-activation Mechanism for SCells in NR CA | ZTE |
| R1-2108930 | Discussion on efficient activation de-activation mechanism for SCells in NR CA | Spreadtrum Communications |
| R1-2109006 | Discussion on efficient activation/de-activation mechanism for Scells | vivo |
| R1-2109099 | Discussion on efficient activation/de-activation for Scell | OPPO |
| R1-2109391 | Discussion on efficient activation and de-activation mechanism for SCell in NR CA | Xiaomi |
| R1-2109519 | Remaining Issues on Scell Activation/Deactivation | Samsung |
| R1-2109637 | On efficient activation/de-activation for SCells | Intel Corporation |
| R1-2109705 | Discussion on efficient activation deactivation mechanism for Scells | NTT DOCOMO, INC. |
| R1-2109896 | Discussion on fast SCell activation/deactivation | InterDigital, Inc. |
| R1-2109988 | Discussion on fast and efficient SCell activation in NR CA | LG Electronics |
| R1-2110060 | On efficient SCell Activation/Deactivation | Apple |
| R1-2110129 | Efficient activation/deactivation of SCell | ASUSTeK |
| R1-2110142 | Reduced Latency SCell Activation | Ericsson |
| R1-2110214 | Efficient activation/de-activation mechanism for SCells in NR CA | Qualcomm Incorporated |
| R1-2110295 | On low latency Scell activation | Nokia, Nokia Shanghai Bell |
| R1-2110490 | Summary#1 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2110491 | Summary#2 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2110592 | Summary#3 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2110657 | Summary#4 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2110658 | Draft LS on triggering signalling of temporary RS for SCell activation | Moderator (Huawei) |
| R1-2110659 | LS on triggering signalling of temporary RS for SCell activation | RAN1, Huawei |
| R1-2110697 | Summary of agreements for Rel-17 feMR-DC WI | WI rapporteur (Huawei) |
| 8.13.3 | Other | |
| R1-2109007 | Discussion on other aspects for DSS | vivo |
| R1-2109392 | Discussion on collision between temporary RS and other signalings | Xiaomi |
| R1-2109757 | Remaining issues on the efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2110143 | CRS Rate-matching and PDCCH enhancement for DSS | Ericsson |
| 8.14 | Study on XR Evaluations for NR (RAN1) | |
| R1-2110215 | TR for Study on XR Evaluations for NR | Qualcomm Incorporated |
| R1-2110621 | Session notes for 8.14 (Study on XR Evaluations for NR) | Ad-Hoc Chair (CMCC) |
| R1-2110677 | TR for Study on XR Evaluations for NR | Rapporteur (Qualcomm) |
| R1-2110678 | TR38.838 v0.1.0 Study on XR (Extended Reality) evaluations for NR | Rapporteur (Qualcomm) |
| R1-2110702 | Session notes for 8.14 (Study on XR Evaluations for NR) | Ad-Hoc Chair (CMCC) |
| 8.14.1 | Performance Evaluation Results | |
| R1-2108736 | Performance evaluation results for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2108799 | XR evaluation results | FUTUREWEI |
| R1-2108869 | Initial evaluation results for XR | CEWiT |
| R1-2108889 | Performance Evaluation Results for XR | ZTE, Sanechips |
| R1-2109008 | Performance evaluation results on XR | vivo |
| R1-2109100 | Evaluation results for XR evaluation | OPPO |
| R1-2109200 | Evaluation results of XR performance | CATT |
| R1-2109307 | Performance evaluation results for XR | CMCC |
| R1-2109393 | Performance evaluation result for XR | Xiaomi |
| R1-2109555 | Performance Evaluation Results | MediaTek Inc. |
| R1-2109638 | Performance evaluation results for XR and CG | Intel Corporation |
| R1-2109737 | Performance results in indoor hotspot and dense urban deployments of CG and VR/AR applications | Nokia, Nokia Shanghai Bell |
| R1-2109922 | XR Performance Evaluation Results | AT&T |
| R1-2109924 | Performance Evaluation Results for XR | InterDigital, Inc. |
| R1-2110144 | XR performance evaluation results | Ericsson |
| R1-2110216 | Evaluation Results for XR Capacity, UE Power, and Coverage | Qualcomm Incorporated |
| R1-2110246 | Initial performance evaluation results of XR | ITRI |
| R1-2110386 | Performance results in indoor hotspot and dense urban deployments of CG and VR/AR applications | Nokia, Nokia Shanghai Bell |
| R1-2110394 | Performance Evaluation Results for XR | InterDigital, Inc. |
| R1-2110401 | Performance evaluation results for XR and CG | Intel Corporation |
| R1-2110402 | Evaluation Results for XR Capacity, UE Power, and Coverage | Qualcomm Incorporated |
| R1-2110403 | XR performance evaluation results | Ericsson |
| R1-2110486 | [DRAFT] Observations for XR capacity evaluations in TR | Moderators (Qualcomm, vivo) |
| R1-2110682 | [DRAFT] Observations for XR capacity evaluations in TR | Rapporteur (Qualcomm) |
| R1-2110683 | [DRAFT] Observations for XR power evaluations in TR | Rapporteur (Qualcomm) |
| R1-2110684 | [DRAFT] Observations for XR coverage evaluations in TR | Rapporteur (Qualcomm) |
| 8.14.2 | Any Remaining Issues on Evaluation Methodology | |
| R1-2108735 | Traffic model and evaluation methodology for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2108890 | Remaining Issues on XR Traffic and Evaluation Methodology | ZTE, Sanechips |
| R1-2109009 | Remaining issues on traffic model and EVM for XR | vivo |
| R1-2109101 | Remaining issues on XR traffic model and evaluation methodology | OPPO |
| R1-2109111 | Remaining issues on evaluation methodology | Ericsson |
| R1-2109198 | Remaining issues of XR Evaluation methodology | CATT |
| R1-2109394 | Discussion on remaining issues of evaluation methodology for XR services | Xiaomi |
| R1-2109520 | Remaining issues on evaluation methodology for XR | Samsung |
| R1-2109552 | Remaining issues on evaluation methodology for XR and CG | MediaTek Inc. |
| R1-2109639 | On remaining issues of evaluation methodology for XR | Intel Corporation |
| R1-2109706 | Discussion on evaluation methodology for XR | NTT DOCOMO, INC. |
| R1-2109738 | Development of the Evaluation Methodology for XR Study | Nokia, Nokia Shanghai Bell |
| R1-2109925 | Remaining Issues on XR Evaluation Methodology | InterDigital, Inc. |
| R1-2109989 | Remaining issues on evaluation methodology for XR | LG Electronics |
| R1-2110061 | Remaining issues on XR evaluation methodology | Apple |
| R1-2110217 | Remaining Issues on Evaluation Methodology for XR | Qualcomm Incorporated |
| R1-2110485 | Summary #1 on remaining issues of traffic model and evaluation methodology for XR | Moderator (vivo) |
| R1-2110553 | Summary #2 on remaining issues of traffic model and evaluation methodology for XR | Moderator (vivo) |
| R1-2110675 | Summary on [106bis-e-NR-XR-02] Email discussion/approval on remaining issues on XR evaluation methodology | Moderator (vivo) |
| 8.14.3 | Others | |
| R1-2108891 | On Capacity and Power Working Areas for XR | ZTE, Sanechips |
| R1-2109010 | Potential enhancement areas for XR | vivo |
| R1-2109102 | Discussion on support of XR/CG service | OPPO |
| R1-2109112 | Discussion on enhancements for XR | Ericsson |
| R1-2109137 | Potential enhancements of NR to support XR services | NEC |
| R1-2109199 | Potential area of NR enhancement for the support of XR services | CATT |
| R1-2109395 | Discussion on potential enhancement for supporting XR | Xiaomi |
| R1-2109521 | Potential enhancements for XR | Samsung |
| R1-2109556 | Further Potential XR Enhancements | MediaTek Inc. |
| R1-2109739 | Enhancements for better XR support over NR | Nokia, Nokia Shanghai Bell |
| R1-2109745 | Challenges and potential enhancements for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2109803 | Discussion on potential enhancements for XR | Sony |
| R1-2109926 | Discussion on potential enhancements for XR | InterDigital, Inc. |
| R1-2110062 | Potential enhancements for XR in Rel-18 | Apple |
| R1-2110218 | Potential Enhancements for XR | Qualcomm Incorporated |
| R1-2110519 | Potential enhancements for XR in Rel-18 | Apple |
| 8.15 | NB-IoT/eMTC support for Non-Terrestrial Network | |
| R1-2110622 | Session notes for 8.15 (Study on NB-IoT/eMTC support for Non-Terrestrial Network) | Ad-Hoc Chair (Ericsson) |
| R1-2110628 | Summary of [106bis-e-R17-RRC-IoT-NTN] IoT over NTN | Moderator (MediaTek) |
| R1-2110629 | List of IoT over NTN Rel-17 RRC parameters | Moderator (MediaTek) |
| R1-2110672 | 3GPP TSG-RAN WG1 Agreements for Release-17 IoT NTN (post RAN1#106-bis-e) | WI rapporteur (MediaTek) |
| 8.15.1 | Enhancements to time and frequency synchronization | |
| R1-2108750 | Discussion on time and frequency synchronization enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2108931 | Discussion on enhancements to time and frequency synchronization for IOT NTN | Spreadtrum Communications |
| R1-2109011 | Discussion on time and frequency synchronization enhancements for NB-IoT/eMTC over NTN | vivo |
| R1-2109080 | Discussion on enhancements to time and frequency synchronization | OPPO |
| R1-2109115 | Enhancements to time and frequency synchronization | Mavenir |
| R1-2109171 | Enhancements to time and frequency synchronization for IoT NTN | MediaTek Inc. |
| R1-2109173 | Summary #1 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek Inc.) |
| R1-2109176 | Enhancements to time and frequency synchronization | Qualcomm Incorporated |
| R1-2109201 | Time and frequency synchronization enhancement for IoT over NTN | CATT |
| R1-2109265 | Enhancement to time and frequency synchronization for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2109308 | Enhancements on time and frequency synchronization for IoT NTN | CMCC |
| R1-2109321 | Time and frequency synchronization for IoT NTN | Lenovo, Motorola Mobility |
| R1-2109362 | Enhancements to time and frequency synchronization | NEC |
| R1-2109396 | Discussion on time and frequency synchronization for IoT NTN | Xiaomi |
| R1-2109522 | On enhancements to time and frequency synchronization | Samsung |
| R1-2109640 | On synchronization for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2109804 | Enhancement to time synchronisation for IoT-NTN | Sony |
| R1-2109829 | Enhancements to time and frequency synchronization to NB-IoT NTN | FGI, Asia Pacific Telecom, III, ITRI |
| R1-2109847 | Discussion on synchronization for IoT-NTN | ZTE |
| R1-2109956 | On time and frequency synchronization enhancements for IoT NTN | Ericsson |
| R1-2110063 | Discussion on Time and Frequency Synchronization in IoT NTN | Apple |
| R1-2110260 | Enhancements to time and frequency synchronization | Nordic Semiconductor ASA |
| R1-2110508 | Summary #2 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek Inc.) |
| R1-2110536 | Summary#3 of AI 8.15.1 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| R1-2110550 | Summary#4 of AI 8.15.1 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| R1-2110645 | Summary#5 of AI 8.15.1 Enhancements to time and frequency synchronization | Moderator (MediaTek) |
| R1-2110652 | DRAFT LS on Validity Timer for UL Synchronization for IoT NTN | Moderator (MediaTek) |
| R1-2110673 | LS on Validity Timer for UL Synchronization | RAN1, MediaTek |
| 8.15.2 | Timing relationship enhancements | |
| R1-2108751 | Discussion on timing relationship enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2108932 | Discussion on timing relationship enhancements for IOT NTN | Spreadtrum Communications |
| R1-2109012 | Discussion on timing relationship enhancements for NB-IoT/eMTC over NTN | vivo |
| R1-2109081 | Discussion on timing relationship enhancements | OPPO |
| R1-2109116 | Timing relationship enhancements | Mavenir |
| R1-2109172 | Timing relationship enhancements for IoT NTN | MediaTek Inc. |
| R1-2109177 | Timing relationship enhancements | Qualcomm Incorporated |
| R1-2109202 | Timing relationship enhancement for IoT over NTN | CATT |
| R1-2109266 | Timing relationship enhancements for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2109309 | Discussion on timing relationship enhancements for IoT NTN | CMCC |
| R1-2109322 | Timing Relationship for IoT NTN | Lenovo, Motorola Mobility |
| R1-2109397 | Discussion on the timing relationship enhancement for IoT NTN | Xiaomi |
| R1-2109523 | Timing relationship enhancements | Samsung |
| R1-2109641 | On timing relationship for NB-IoT and eMTC NTN | Intel Corporation |
| R1-2109805 | Timing relationships enhancement for IoT- NTN | Sony |
| R1-2109830 | Timing relationship enhancements to NB-IoT NTN | FGI, Asia Pacific Telecom, III, ITRI |
| R1-2109848 | Discussion on timing relationship for IoT-NTN | ZTE |
| R1-2109957 | On timing relationship enhancements for IoT NTN | Ericsson |
| R1-2110064 | Discussion on Timing Relationship Enhancements in IoT NTN | Apple |
| R1-2110262 | Timing relationship enhancements | Nordic Semiconductor ASA |
| R1-2110461 | FL summary 1 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2110462 | FL summary 2 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2110533 | FL summary 3 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2110534 | FL summary 4 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| 8.15.3 | Other | |
| R1-2109267 | Discussion on other aspects for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2109398 | Discussion on the other design aspects for IoT NTN | Xiaomi |
| R1-2109750 | Other aspects to support IoT in NTN | Huawei, HiSilicon |
| R1-2109849 | Discussion on additional enhancement for IoT-NTN | ZTE |
| R1-2109958 | Mobile IoT in the 5G future – NB-IoT and eMTC for NTN | Ericsson |
| 8.16 | New Bands and Bandwidth Allocation for LTE based 5G Terrestrial Broadcast | |
| R1-2110623 | Session notes for 8.16 (New Bands and Bandwidth Allocation for LTE based 5G Terrestrial Broadcast) | Ad-Hoc Chair (Ericsson) |
| R1-2110666 | Summary of agreements for LTE based 5G Terrestrial Broadcast | WI rapporteur (Qualcomm incorporated) |
| 8.16.1 | PMCH allocation of 6/7/8 MHz and corresponding MBSFN reference signals | |
| R1-2108857 | TP on PMCH allocation and corresponding MBSFN reference signals | ZTE |
| R1-2109178 | PMCH allocation of 6/7/8MHz | Qualcomm Incorporated |
| R1-2110371 | Flexible PMCH bandwidth allocation for the 15KHz subcarrier spacing | Huawei, HiSilicon |
| R1-2110542 | Summary of [106bis-e-LTE-5G-Terr-Bcast-01] | Moderator (Qualcomm) |
| 8.17 | Rel-17 UE Features | |
| R1-2110587 | Updated RAN1 UE features list for Rel-17 NR after RAN1 #106bis-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2110588 | Updated RAN1 UE features list for Rel-17 LTE after RAN1 #106bis-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| 8.17.1 | UE features for further enhancements on NR-MIMO | |
| R1-2108798 | UE features for further enhancements on NR-MIMO | FUTUREWEI |
| R1-2108884 | UE features for feMIMO | ZTE |
| R1-2109013 | Discussion on UE features for further enhancements on NR-MIMO | vivo |
| R1-2109046 | UE features for further enhancements on NR-MIMO | OPPO |
| R1-2109143 | Rel-17 UE features for further NR MIMO enhancements | Huawei, HiSilicon |
| R1-2109203 | On Rel-17 FeMIMO UE features | CATT |
| R1-2109524 | UE features for Rel-17 NR FeMIMO | Samsung |
| R1-2109549 | UE features for further enhancements on NR MIMO | MediaTek Inc. |
| R1-2109642 | UE features for feMIMO | Intel Corporation |
| R1-2109912 | Summary of UE features for further enhancements on NR-MIMO | Moderator (AT&T) |
| R1-2109939 | Discussion on UE features for FeMIMO | Lenovo, Motorola Mobility |
| R1-2110065 | Views on Rel-17 FeMIMO UE features | Apple |
| R1-2110219 | Discussion on FeMIMO UE features | Qualcomm Incorporated |
| R1-2110264 | On UE features for further enhancements on NR-MIMO | Nokia, Nokia Shanghai Bell |
| R1-2110293 | UE features for feMIMO | Ericsson |
| 8.17.2 | UE features for supporting NR from 52.6 GHz to 71 GHz | |
| R1-2108834 | UE features for supporting NR from 52.6 GHz to 71 GHz | FUTUREWEI |
| R1-2108941 | Discussion on UE features for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2109014 | Discussions on UE features for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2109144 | Rel-17 UE features for extension to 71 GHz | Huawei, HiSilicon |
| R1-2109441 | UE features for extending current NR operation to 71 GHz | Ericsson |
| R1-2109525 | UE features for supporting NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2109563 | Views on UE features for supporting NR from 52.6 GHz to 71 GHz | MediaTek Inc. |
| R1-2109643 | Discussion on UE capability for extending NR up to 71 GHz | Intel Corporation |
| R1-2109707 | Views on Rel-17 UE features for supporting NR from 52.6 GHz to 71 GHz | NTT DOCOMO, INC. |
| R1-2109719 | Views on applicability of Rel-15/16 NR UE features to FR2-2 | NTT DOCOMO, INC. |
| R1-2109913 | Summary of UE features for supporting NR from 52.6 GHz to 71 GHz | Moderator (AT&T) |
| R1-2109969 | Discussion on UE features for NR above 52.6 GHz | LG Electronics |
| R1-2110066 | Views on UE features for supporting NR from 52.6 GHz to 71 GHz | Apple |
| R1-2110220 | UE features for NR from 52.6 GHz to 71 GHz | Qualcomm Incorporated |
| R1-2110265 | On UE features for supporting NR from 52.6 GHz to 71 GHz | Nokia, Nokia Shanghai Bell |
| 8.17.3 | UE features for enhanced IIoT and and URLLC | |
| R1-2108858 | Discussion on UE features for enhanced IIoT and URLLC | ZTE |
| R1-2109015 | Discussion on UE features for IIoT and URLLC | vivo |
| R1-2109145 | Rel-17 UE features for enhanced IIoT/URLLC | Huawei, HiSilicon |
| R1-2109526 | UE features for enhanced IIoT and URLLC | Samsung |
| R1-2109578 | Views on UE features for enhanced IIoT and URLLC | MediaTek Inc. |
| R1-2109644 | Discussion on UE features for URLLC/IIOT | Intel Corporation |
| R1-2109708 | Discussion on Rel.17 UE features for enhanced IIoT/URLLC | NTT DOCOMO, INC. |
| R1-2109709 | Summary on UE features for enhanced IIoT and URLLC | Moderator (NTT DOCOMO, INC.) |
| R1-2109725 | Rel-17 UE Features for IIoT/URLLC | Ericsson Inc. |
| R1-2110067 | Views on UE features for Rel-17 enhanced IIoT and URLLC | Apple |
| R1-2110221 | UE features for enhanced IIOT and URLLC | Qualcomm Incorporated |
| R1-2110266 | On UE features for enhanced IIoT and and URLLC | Nokia, Nokia Shanghai Bell |
| 8.17.4 | UE features for NR NTN | |
| R1-2109146 | Rel-17 UE features for NR NTN | Huawei, HiSilicon |
| R1-2109400 | Discussion on Rel-17 UE features for NTN | Xiaomi |
| R1-2109527 | UE features for NR NTN | Samsung |
| R1-2109645 | UE features for NR NTN | Intel Corporation |
| R1-2109850 | Discussion on UE feature for NR-NTN | ZTE |
| R1-2109914 | Summary of UE features for NR NTN | Moderator (AT&T) |
| R1-2109931 | On UE features for NR NTN | Ericsson |
| R1-2110068 | Views on NR NTN UE Features | Apple |
| R1-2110222 | UE features for NR NTN | Qualcomm Incorporated |
| R1-2110267 | On UE features for NR NTN | Nokia, Nokia Shanghai Bell |
| R1-2110308 | Considerations on Rel-17 UE features for NR NTN | SoftBank Corp. |
| 8.17.5 | UE features for NR positioning enhancements | |
| R1-2108885 | UE features for NR positioning enhancements | ZTE |
| R1-2109016 | Discussion on UE features for NR positioning enhancements | vivo |
| R1-2109057 | UE features for NR positioning enhancements | OPPO |
| R1-2109147 | Rel-17 UE features for NR positioning enhancements | Huawei, HiSilicon |
| R1-2109205 | Discussion on Rel-17 UE features for NR Positioning enhancements | CATT |
| R1-2109528 | UE features for NR positioning enhancements | Samsung |
| R1-2109646 | UE features for NR positioning enhancement | Intel Corporation |
| R1-2109915 | Summary of UE features for NR positioning enhancements | Moderator (AT&T) |
| R1-2110223 | Discussion on Positioning Enhancements Features | Qualcomm Incorporated |
| R1-2110268 | On UE features for NR positioning enhancements | Nokia, Nokia Shanghai Bell |
| R1-2110347 | Views on NR positioning Enhancements UE features | Ericsson |
| 8.17.6 | UE features for REDCAP | |
| R1-2108789 | UE features for REDCAP | FUTUREWEI |
| R1-2108825 | UE features for RedCap | Ericsson |
| R1-2108933 | UE features for RedCap | Spreadtrum Communications |
| R1-2109017 | Discussion on UE features for NR REDCAP | vivo, Guangdong Genius |
| R1-2109148 | Rel-17 UE features for RedCap | Huawei, HiSilicon |
| R1-2109339 | Discussion on RedCap UE features | ZTE, Sanechips |
| R1-2109529 | UE features for RedCap | Samsung |
| R1-2109579 | Views on UE features for RedCap | MediaTek Inc. |
| R1-2109647 | On UE features for RedCap | Intel Corporation |
| R1-2109710 | Discussion on UE features for RedCap | NTT DOCOMO, INC. |
| R1-2109711 | Summary on UE features for REDCAP | Moderator (NTT DOCOMO, INC.) |
| R1-2110069 | Views on UE Features for Redcap | Apple |
| R1-2110224 | UE features for RedCap | Qualcomm Incorporated |
| R1-2110269 | On UE features for REDCAP | Nokia, Nokia Shanghai Bell |
| R1-2110382 | FL summary on incoming LS on capability related RAN2 agreements for RedCap | Moderator (Ericsson) |
| 8.17.7 | UE features for UE power saving enhancements | |
| R1-2109018 | Discussion on UE features for UE power saving enhancements | vivo |
| R1-2109149 | Rel-17 UE features for UE power saving enhancements | Huawei, HiSilicon |
| R1-2109206 | Discussion on UE feature of UE Power saving enhancements for NR | CATT |
| R1-2109530 | UE features for UE power saving enhancements | Samsung |
| R1-2109553 | On UE features for UE power saving enhancements | MediaTek Inc. |
| R1-2109585 | On UE features for UE power saving enhancements | MediaTek Inc. |
| R1-2109648 | Discussion on UE features for UE power saving | Intel Corporation |
| R1-2109712 | Discussion on Rel-17 UE features for UE power saving | NTT DOCOMO, INC. |
| R1-2109713 | Summary on UE features for UE power saving enhancements | Moderator (NTT DOCOMO, INC.) |
| R1-2109724 | Discussion on UE feature for UE power saving enhancements | ZTE, Sanechips |
| R1-2110070 | Views on UE features for Rel-17 UE power saving | Apple |
| R1-2110145 | UE features for UEPS | Ericsson |
| R1-2110225 | UE features for UE power saving enhancements | Qualcomm Incorporated |
| R1-2110270 | On UE features for UE power saving enhancements | Nokia, Nokia Shanghai Bell |
| 8.17.8 | UE features for NR coverage enhancement | |
| R1-2108859 | Discussion on UE features for NR coverage enhancement | ZTE |
| R1-2109019 | Discussion on UE features for NR coverage enhancement | vivo |
| R1-2109150 | Rel-17 UE features for NR coverage enhancement | Huawei, HiSilicon |
| R1-2109531 | UE features for NR coverage enhancement | Samsung |
| R1-2109649 | Discussion on UE features for NR coverage enhancement | Intel Corporation |
| R1-2109714 | Summary on UE features for NR coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2110007 | UE feature for Rel-17 coverage enhancement | Sharp |
| R1-2110128 | UE Features for NR Coverage Enhancement | Ericsson |
| R1-2110226 | UE Features for Coverage Enhancements | Qualcomm Incorporated |
| R1-2110271 | On UE features for NR coverage enhancement | Nokia, Nokia Shanghai Bell |
| R1-2110375 | Discussion on UE features for NR Coverage Enhancement | MediaTek Inc. |
| 8.17.9 | UE features for NB-IoT and LTE-MTC enhancements | |
| R1-2109151 | Rel-17 UE features for NB-IoT and LTE-MTC enhancements | Huawei, HiSilicon |
| R1-2109340 | Discussion on LTE-M and NB-IoT UE features | ZTE, Sanechips |
| R1-2109715 | Summary on UE features for NB-IoT and LTE-MTC enhancements | Moderator (NTT DOCOMO, INC.) |
| R1-2110227 | UE features for NB-IoT and LTE-MTC enhancements | Qualcomm Incorporated |
| R1-2110319 | On UE features for NB-IoT and LTE-MTC enhancements | Ericsson |
| 8.17.10 | UE features for IAB enhancements | |
| R1-2109020 | Discussion on UE features for IAB enhancements | vivo |
| R1-2109152 | Rel-17 UE features for IAB enhancements | Huawei, HiSilicon |
| R1-2109264 | Discussion on NR Rel-17 IAB MT Features | ZTE, Sanechips |
| R1-2109532 | UE features for NR IAB | Samsung |
| R1-2109650 | UE features for IAB enhancement | Intel Corporation |
| R1-2109916 | Summary of UE features for IAB enhancements | Moderator (AT&T) |
| R1-2110228 | UE features for IAB enhancements | Qualcomm Incorporated |
| R1-2110272 | On UE features for IAB enhancements | Nokia, Nokia Shanghai Bell |
| R1-2110334 | UE features for enhanced IAB | Ericsson |
| 8.17.11 | UE features for NR sidelink enhancement | |
| R1-2108835 | UE features for NR sidelink enhancement | FUTUREWEI |
| R1-2109021 | UE features for NR sidelink enhancement | vivo |
| R1-2109066 | On UE feature list for NR sidelink enhancement | OPPO |
| R1-2109153 | Rel-17 UE features for NR sidelink enhancement | Huawei, HiSilicon |
| R1-2109204 | Discussion on Rel-17 UE features for sidelink enhancements | CATT, GOHIGH |
| R1-2109399 | Discussion on Rel-17 UE features on sidelink enhancement | Xiaomi |
| R1-2109533 | UE features for NR sidelink enhancement | Samsung |
| R1-2109565 | Views on UE features for NR sidelink enhancements | MediaTek Inc. |
| R1-2109651 | UE features for NR SL enhancement | Intel Corporation |
| R1-2109716 | Summary on UE features for NR sidelink enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2109733 | Discussion on UE features for NR sidelink Enhancement | ZTE, Sanechips |
| R1-2109862 | Discussion on UE features for NR sidelink enhancement | LG Electronics |
| R1-2110071 | Views on NR Sidelink Enhancement UE Features | Apple |
| R1-2110229 | UE Features for Sidelink Enhancements | Qualcomm Incorporated |
| R1-2110273 | On UE features for NR sidelink enhancement | Nokia, Nokia Shanghai Bell |
| R1-2110342 | UE features for NR sidelink enhancement | Ericsson |
| 8.17.12 | UE features for NR MBS | |
| R1-2108860 | Discussion on Rel-17 UE features for NR MBS | ZTE |
| R1-2109022 | Discussion on UE features for MBS | vivo |
| R1-2109154 | Rel-17 UE features for NR MBS | Huawei, HiSilicon |
| R1-2109534 | UE features for NR MBS | Samsung |
| R1-2109570 | Views on UE features for NR MBS | MediaTek Inc. |
| R1-2109652 | Discussion on UE Features for NR MBS | Intel Corporation |
| R1-2109717 | Summary on UE features for NR MBS | Moderator (NTT DOCOMO, INC.) |
| R1-2110230 | UE features for MBS | Qualcomm Incorporated |
| R1-2110274 | On UE features for NR MBS | Nokia, Nokia Shanghai Bell |
| R1-2110348 | views on NR MBS UE features | Ericsson |
| 8.17.13 | UE features for DSS | |
| R1-2108861 | Discussion on Rel-17 UE features for DSS | ZTE |
| R1-2109023 | discussion on UE features for DSS | vivo |
| R1-2109155 | Rel-17 UE features for DSS | Huawei, HiSilicon |
| R1-2109535 | UE features for DSS | Samsung |
| R1-2109554 | On UE features for DSS | MediaTek Inc. |
| R1-2109653 | UE features for DSS | Intel Corporation |
| R1-2109917 | Summary of UE features for DSS | Moderator (AT&T) |
| R1-2110072 | Views on Rel-17 eDSS UE features | Apple |
| R1-2110146 | UE features for DSS and CA Enhancements | Ericsson |
| R1-2110231 | UE features for DSS and LTE_NR_DC_enh2 | Qualcomm Incorporated |
| R1-2110275 | On UE features for DSS and LTE NR DC enhancements | Nokia, Nokia Shanghai Bell |
| 8.17.14 | UE features for IoT over NTN | |
| R1-2109156 | Rel-17 UE features for IoT over NTN | Huawei, HiSilicon |
| R1-2109536 | UE features for IoT over NTN | Samsung |
| R1-2109654 | UE features for IOT over NTN | Intel Corporation |
| R1-2109851 | Discussion on UE feature for IoT-NTN | ZTE |
| R1-2109918 | Summary of UE features for IoT over NTN | Moderator (AT&T) |
| R1-2109959 | On UE features for IoT over NTN | Ericsson |
| R1-2110073 | Views on IoT over NTN UE Features | Apple |
| R1-2110232 | UE features for IoT over NTN | Qualcomm Incorporated |
| R1-2110276 | On UE features for IoT over NTN | Nokia, Nokia Shanghai Bell |
| R1-2110309 | Considerations on Rel-17 UE features for IoT over NTN | SoftBank Corp. |
| 8.17.15 | UE features for LTE based 5G terrestrial broadcast | |
| R1-2108862 | Discussion on Rel-17 UE features for LTE based 5G terrestrial broadcast | ZTE |
| R1-2109157 | Rel-17 UE features for LTE-based 5G terrestrial broadcast | Huawei, HiSilicon |
| R1-2109718 | Summary on UE features for LTE based 5G terrestrial broadcast | Moderator (NTT DOCOMO, INC.) |
| R1-2110233 | UE features for LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
| R1-2110277 | On UE features for LTE based 5G terrestrial broadcast | Nokia, Nokia Shanghai Bell |
| 8.17.16 | UE features for DL 1024QAM for NR FR1 | |
| R1-2109158 | Rel-17 UE features for NR DL 1024-QAM | Huawei, HiSilicon |
| R1-2109537 | UE features for DL 1024QAM for NR FR1 | Samsung |
| R1-2109655 | UE features for DL 1024QAM for NR FR1 | Intel Corporation |
| R1-2109723 | Discussion on UE feature for 1024QAM | ZTE, Sanechips |
| R1-2109919 | Summary of UE features for DL 1024QAM for NR FR1 | Moderator (AT&T) |
| R1-2110147 | UE features for 1024QAM | Ericsson |
| R1-2110234 | UE features for DL 1024 QAM for NR FR1 | Qualcomm Incorporated |
| R1-2110278 | On UE features for DL 1024QAM for NR FR1 | Nokia, Nokia Shanghai Bell |
| 8.17.17 | Other | |
| R1-2109140 | Discussion on Rel-17 UE features for UL Tx switching | ZTE |
| R1-2109656 | UE features - others | Intel Corporation |
| R1-2109720 | Summary on other UE feature related discussions | Moderator (NTT DOCOMO, INC.) |
| 8.18 | Other | |
| R1-2108737 | Enhancements on the scheduling of PUSCH | Huawei, HiSilicon, China Unicom, Ericsson |
| R1-2108886 | TEI-17 proposal on NR codeword mapping | ZTE |
| R1-2109024 | Rel-17 TEI proposal | vivo |
| R1-2109047 | Support of default power control parameter per TRP | OPPO |
| R1-2109207 | Rel-17 TEI proposals on SSB resource for RLM and HARQ-ACK feedback enhancements for TDD-FDD CA | CATT |
| R1-2109657 | Rel-17 TEI proposal for mitigating half-duplex issue in NR V2X groupcast NACK-only case | Intel Corporation, Qualcomm, NTT DOCOMO, Ericsson, Bosch |
| R1-2109721 | NR positioning support for TA-based positioning in E-CID (TEI) | NTT DOCOMO INC., Ericsson, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, CATT, Nokia |
| R1-2109722 | Summary on Rel-17 TEIs | Moderator (NTT DOCOMO, INC.) |
| R1-2109835 | TEI-17 proposal targeting the false PMI reporting issue | Ericsson |
| R1-2110235 | Rel-17 TEI | Qualcomm Incorporated |
| R1-2110263 | On Rel-17 RAN1 PHY Freeze | MediaTek Inc. |
| R1-2110552 | [Draft] LS on NR Positioning support for TA measurement in NR UL E-CID | NTT DOCOMO |
| R1-2110601 | LS on NR Positioning support for TA measurement in NR UL E-CID | RAN1, NTT DOCOMO |
| R1-2110686 | List of RAN1 agreements for Rel-17 WI on NR DL 1024QAM | WI rapporteur (Ericsson) |
| 9 | Election | |
| R1-2108695 | Guidance for RAN1 vice-chair election during TSG RAN WG1#106bis-e | RAN1 Chair, ETSI MCC |
| 10 | Closing of the meeting | |
| R1-2110611 | Thank you Havish! | All of us in RAN1 |